Digital exposure report
mtu.edu
Critical findings in the observed public configuration. Some basic protections were not detected.
Scanned: 2026-11-17 23:03 UTC
Full coverage: every applicable check was assessed.
What to do first
- 1.
Tell receiving mail servers how to treat fake email from your domain
Without this policy, inboxes have less guidance for spotting messages that impersonate you.
Who can fix it: Your email provider, together with whoever manages your DNS
How to verify after the fix
dig +short TXT _dmarc.mtu.edu
- 2.
Tell browsers to always use the secure version
Helps browsers use HTTPS on future visits after they have received the policy.
Who can fix it: Your web host
How to verify after the fix
curl -sIL https://mtu.edu/ | grep -i "Strict-Transport-Security"
A starting point, not a security guarantee.
What this grade means
- Tested hostname
- mtu.edu
- Website request
- GET https://mtu.edu/ → https://www.mtu.edu/
- Scan time
- 2026-11-17 23:03:12 UTC
- Grading method
- Version 2How grading works
- Unverified or excluded checks
- None. Every applicable check was assessed.
This is a snapshot of the public configuration checks listed in this report. It does not verify the site's owner, business legitimacy, application security, or absence of vulnerabilities. It is not a security certification.
Score by category
| Email security | 19/30 | Spoofing email in the company's name is possible in some cases. |
| Encryption & certificate | 25/25 | Traffic to the site is encrypted and the certificate is valid. |
| Browser protections | 5/30 | Several browser hardening headers are missing, which removes layers of protection against script injection and framing. |
| DNS infrastructure | 8/15 | The domain's infrastructure works, but recommended hardening is missing. |
Fix priorities
- 1.HighHSTS — enforce encryption in the browser · Hardening gap+8
- 2.MediumDMARC — anti-spoofing policy · Hardening gap+10
- 3.MediumDNSSEC — signed DNS records · Hardening gap+7
- 4.MediumCSP — protection from script injection · Hardening gap+8
- 5.LowX-Content-Type-Options · Hardening gap+4
- 6.LowReferrer-Policy · Hardening gap+3
- 7.LowPermissions-Policy · Hardening gap+2
- 8.LowSoftware version disclosure · Hardening gap
Findings
SPF — who may send mail for the domain
Passed · Severity: OK · 9/10An authorized sender list is defined; mail from other servers is flagged as suspicious.
~all (softfail) — acceptable when combined with enforced DMARC. 5 of 10 DNS lookups.
v=spf1 ip4:141.219.0.0/16 include:secure.giftlegacy.com include:_spf.google.com include:emailsrvr.com include:e2ma.net include:spf.watermarkinsights.com ip4:209.61.151.0/24 ip4:166.78.68.0/22 ip4:198.61.254.0/23 ip4:192.237.158.0/23 ip4:23.253.182.0/23 ip4:104.130.96.0/28 ip4:146.20.113.0/24 ip4:146.20.191.0/24 ip4:159.135.224.0/20 ip4:69.72.32.0/20 ip4:104.130.122.0/23 ip4:146.20.112.0/26 ip4:161.38.192.0/20 ip4:143.55.224.0/21 ip4:143.55.232.0/22 ip4:159.112.240.0/20 ip4:198.244.48.0/20 ip4:204.220.168.0/21 ip4:204.220.176.0/20 ip4:38.106.32.22/32 ip4:38.106.32.46/32 ip4:54.240.121.247 ip4:54.240.121.248 ip4:103.237.104.0/22 ip4:104.47.0.0/17 ip4:13.111.0.0/20 ip4:132.174.100.123 ip4:132.174.100.127 ip4:132.174.100.128 ip4:132.174.100.129 ip4:132.174.129.13 ip4:132.174.29.192/27 ip4:134.170.132.0/24 ip4:134.170.140.0/24 ip4:136.146.128.64/27 ip4:136.146.208.16/28 ip4:136.146.210.16/28 ip4:136.147.128.0/20 ip4:136.147.176.0/20 ip4:136.147.182.0/24 ip4:136.147.46.192/26 ip4:136.147.62.192/26 ip4:139.146.146.128/25 ip4:139.146.160.0/25 ip4:157.55.133.0/25 ip4:157.55.158.0/23 ip4:157.55.234.0/24 ip4:157.56.110.0/23 ip4:157.56.112.0/24 ip4:157.56.116.0/25 ip4:157.56.120.0/25 ip4:157.56.87.192/26 ip4:162.247.216.0/22 ip4:167.89.0.0/17 ip4:173.193.132.0/23 ip4:173.203.2.0/25 ip4:173.203.6.0/23 ip4:174.137.46.0/24 ip4:174.36.80.208/28 ip4:174.36.84.12 ip4:174.36.84.14/31 ip4:174.36.84.245 ip4:174.36.84.32 ip4:174.36.92.96/27 ip4:182.50.78.64/28 ip4:185.12.80.0/22 ip4:185.28.196.0/22 ip4:188.172.128.0/20 ip4:192.161.144.0/20 ip4:192.254.112.0/20 ip4:192.28.128.0/18 ip4:192.41.76.4 ip4:192.41.90.128/26 ip4:192.87.104.130 ip4:192.87.44.30 ip4:193.240.184.6 ip4:193.240.184.7 ip4:198.137.189.11 ip4:198.137.190.123 ip4:198.187.195.89 ip4:198.187.196.0/24 ip4:198.21.0.0/21 ip4:198.245.80.0/20 ip4:198.37.144.0/20 ip4:199.106.139.112/28 ip4:199.122.120.0/21 ip4:199.15.212.0/22 ip4:199.244.78.223 ip4:199.244.78.224 ip4:199.91.136.26 ip4:199.91.136.28 ip4:199.91.140.26 ip4:204.14.232.64/28 ip4:204.14.234.64/28 ip4:204.14.238.0/27 ip4:206.107.42.254 ip4:206.152.1.94 ip4:206.79.10.196 ip4:207.126.144.0/20 ip4:207.250.68.0/24 ip4:207.46.100.0/24 ip4:207.46.101.128/26 ip4:207.46.108.0/25 ip4:207.46.163.0/24 ip4:207.46.51.64/26 ip4:207.67.38.0/24 ip4:207.67.98.192/27 ip4:208.117.48.0/20 ip4:208.43.21.28 ip4:208.43.21.66 ip4:208.43.21.70 ip4:209.43.22.0/28 ip4:213.199.154.0/24 ip4:213.199.180.0/24 ip4:213.212.88.171 ip4:216.138.238.192/26 ip4:216.146.46.10 ip4:216.146.46.11 ip4:216.151.85.132 ip4:216.151.85.133 ip4:216.198.0.0/18 ip4:216.32.180.0/23 ip4:217.199.180.36 ip4:23.103.128.0/19 ip4:23.103.191.0/24 ip4:23.103.198.0/23 ip4:23.103.200.0/21 ip4:23.103.208.0/21 ip4:23.229.217.108 ip4:27.111.242.222 ip4:37.188.97.188/32 ip4:40.107.0.0/16 ip4:50.31.32.0/19 ip4:50.57.0.0/27 ip4:52.2.127.126 ip4:52.2.36.135 ip4:59.167.34.100 ip4:62.204.93.131 ip4:63.146.161.230 ip4:64.106.241.148 ip4:64.132.88.0/23 ip4:64.132.92.0/24 ip4:64.18.0.0/20 ip4:64.4.22.64/26 ip4:64.72.147.0/24 ip4:65.55.169.0/24 ip4:65.55.88.0/24 ip4:66.150.160.0/24 ip4:66.18.116.43 ip4:66.231.80.0/20 ip4:66.35.37.96/27 ip4:67.192.241.0/24 ip4:67.228.21.188 ip4:67.228.50.32/27 ip4:68.232.192.0/20 ip4:69.164.120.70 ip4:72.3.185.0/24 ip4:72.32.154.0/24 ip4:72.32.217.0/24 ip4:72.32.243.0/24 ip4:74.115.207.202 ip4:74.115.207.212 ip4:74.115.207.213 ip4:74.206.109.32/27 ip4:74.62.122.128/28 ip4:74.86.113.29 ip4:74.86.207.39 ip4:74.86.236.242 ip4:74.86.241.250 ip4:75.126.200.128/27 ip4:75.126.253.0/24 ip4:80.150.125.180 ip4:80.150.125.181 ip4:85.17.187.195 ip4:85.222.130.192/26 ip4:85.222.138.192/26 ip4:94.236.119.0/26 ip4:95.211.74.199 ip4:96.43.144.64/28 ip4:96.43.147.64/28 ip4:96.43.148.64/28 ip4:96.43.151.64/28 ip4:96.43.152.64/27 ip4:96.43.153.64/27 ip4:96.46.150.192/27 ip4:98.129.184.0/23 ip4:74.122.104.0/22 ip4:72.50.228.0/24 ip4:69.32.224.120/30 ip4:54.240.57.46/31 ip4:159.135.238.30/32 ip4:204.220.188.71/32 ip4:204.220.188.72/30 ip6:2607:f8b0:400c:c10::1b ip6:2800:3f0:4003:c01::1b ip6:2a01:111:f400::/48 ip6:2a04:35c0::/29 ~all
$ dig +short TXT mtu.edu
DMARC — anti-spoofing policy
Needs attention · Severity: Medium · Hardening gap · 5/15DMARC is in monitoring mode only — forged email still reaches recipients.
Policy p=none. p=none collects reports but does not protect.
v=DMARC1; p=none; ruf=mailto:michigantechit@us.cp-dmarc.com; rua=mailto:michigantechit@us.cp-dmarc.com,mailto:2hzorv7s@ag.us.dmarcian.com,mailto:dmarc-report-l@mtu.edu
$ dig +short TXT _dmarc.mtu.edu
- Step 1 (monitoring, no effect on mail): publish p=none with an rua address to receive reports.
- Step 2: analyze reports for 2–4 weeks and make sure every legitimate sender passes SPF/DKIM.
- Step 3: move to p=quarantine, and finally to p=reject.
_dmarc.mtu.edu. TXT "v=DMARC1; p=none; rua=mailto:dmarc@mtu.edu; fo=1"
Safety: DNS changes are made only at your DNS provider. This tool only reads public data and changes nothing on the domain. Jumping straight to reject without a monitoring phase can block legitimate mail.
DKIM — digital signature on email
Passed · Severity: OK · 5/5A DKIM public key is published. On its own this doesn't prove outgoing mail is signed or aligned with your From domain.
DKIM public key found for selector: google, s1, s2. Confirm signing with dkim=pass in a sent message's Authentication-Results.
google._domainkey: v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAm2AW2DpH404dbHZrDXTrTI9tcJre… s1._domainkey: k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwpFTm0NZmoqjJHZgdRAiMKaj6lw6GEWD… s2._domainkey: k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAoy4ocZ5JPNFOk4Swi2gFZ78AffT+N+OK…
$ dig +short TXT google._domainkey.mtu.edu
MX — inbound mail routing
Passed · Severity: OK · unscoredMail exchangers are published for the domain.
5 MX record(s). This shows where inbound mail is routed, not whether mail is sent from the domain.
1 aspmx.l.google.com 10 aspmx2.googlemail.com 5 alt2.aspmx.l.google.com 5 alt1.aspmx.l.google.com 10 aspmx3.googlemail.com
$ dig +short MX mtu.edu
HTTPS available
Passed · Severity: OK · 10/10The site loads over an encrypted connection.
https://mtu.edu/ returned HTTP 200 (final URL: https://www.mtu.edu/). Client-side certificate validation passed.
HTTP 200 Final URL: https://www.mtu.edu/
$ curl -sIL https://mtu.edu/
HTTP → HTTPS redirect
Passed · Severity: OK · 7/7Visitors arriving at an unencrypted address are automatically sent to the secure version.
HTTP 301 → https://www.mtu.edu/
HTTP 301 Location: https://www.mtu.edu/
$ curl -sI http://mtu.edu/ | grep -iE "^(HTTP|location)"
SSL/TLS certificate validity
Passed · Severity: OK · 8/8The certificate was accepted by a validating TLS client at scan time.
Live TLS handshake succeeded. Latest issuance in CT logs: Let's Encrypt, expiring 2027-01-15 (58 days). CT shows issued certificates, not necessarily the one served — confirm dates with the verify command.
Live TLS handshake: certificate accepted CT logs (context only, not scored): Issuer: Let's Encrypt Valid from: 2026-10-17 Valid until: 2027-01-15 Names: *.atbr.mtu.edu, *.bio.mtu.edu, *.cege.mtu.edu, *.chem.mtu.edu, *.cls.mtu.edu, *.cs.mtu.edu Based on Certificate Transparency logs; may not reflect the certificate currently served.
$ echo | openssl s_client -connect mtu.edu:443 -servername mtu.edu 2>/dev/null | openssl x509 -noout -issuer -dates
HSTS — enforce encryption in the browser
Failed · Severity: High · Hardening gap · 0/8Browsers aren't told to always use an encrypted connection, enabling interception attacks on public networks.
No Strict-Transport-Security header. Users are exposed to SSL stripping on the first request.
Strict-Transport-Security: (missing)
$ curl -sIL https://mtu.edu/ | grep -i "Strict-Transport-Security"
- Start with a short max-age (300 seconds) and make sure every subdomain works over HTTPS.
- Gradually raise it to 31536000 (one year) and add includeSubDomains.
- Consider preload only once the policy is stable — removal from the preload list is slow.
/* Strict-Transport-Security: max-age=31536000; includeSubDomains
Safety: This change is made in your server/CDN settings. Test on staging before production. HSTS is cached in the visitor's browser — a long max-age on a site without working HTTPS will block access.
CSP — protection from script injection
Failed · Severity: Medium · Hardening gap · 0/8Missing Content-Security-Policy header: this removes one layer of protection against script injection.
No Content-Security-Policy header found.
Content-Security-Policy: (missing)
$ curl -sIL https://mtu.edu/ | grep -i "Content-Security-Policy"
- First publish Content-Security-Policy-Report-Only — it blocks nothing, it only reports.
- Collect violations for a week or two and tune the policy to your legitimate sources.
- Switch to the Content-Security-Policy header and replace 'unsafe-inline' with a nonce or hash.
/* Content-Security-Policy-Report-Only: default-src 'self'; script-src 'self'; object-src 'none'; base-uri 'self'; frame-ancestors 'self'
Safety: This change is made in your server/CDN settings. Test on staging before production. An overly strict CSP will break scripts — that's why you start in Report-Only mode.
Clickjacking protection
Passed · Severity: OK · 5/5The site can't be embedded by foreign sites.
X-Frame-Options: SAMEORIGIN
X-Frame-Options: SAMEORIGIN
$ curl -sIL https://mtu.edu/ | grep -i "X-Frame-Options"
X-Content-Type-Options
Failed · Severity: Low · Hardening gap · 0/4The browser may interpret files as code unintentionally.
Missing X-Content-Type-Options: nosniff header (MIME sniffing).
X-Content-Type-Options: (missing)
$ curl -sIL https://mtu.edu/ | grep -i "X-Content-Type-Options"
- Add X-Content-Type-Options: nosniff to every response.
/* X-Content-Type-Options: nosniff
Safety: This change is made in your server/CDN settings. Test on staging before production.
Referrer-Policy
Failed · Severity: Low · Hardening gap · 0/3Internal URLs (including parameters) may leak to external sites.
Referrer-Policy is missing; the browser will use its default.
Referrer-Policy: (missing)
$ curl -sIL https://mtu.edu/ | grep -i "Referrer-Policy"
- Set Referrer-Policy: strict-origin-when-cross-origin.
/* Referrer-Policy: strict-origin-when-cross-origin
Safety: This change is made in your server/CDN settings. Test on staging before production.
Permissions-Policy
Needs attention · Severity: Low · Hardening gap · 0/2Access to sensitive features like the camera and location isn't restricted.
Missing Permissions-Policy header.
Permissions-Policy: (missing)
$ curl -sIL https://mtu.edu/ | grep -i "Permissions-Policy"
- Disable browser features the site doesn't need (camera, microphone, geolocation).
/* Permissions-Policy: camera=(), microphone=(), geolocation=()
Safety: This change is made in your server/CDN settings. Test on staging before production. Don't disable a feature the site actually uses.
Software version disclosure
Needs attention · Severity: Low · Hardening gap · unscoredThe server discloses its software version, making it easier for attackers to find known vulnerabilities.
Headers with a version number: x-powered-by: PHP/8.2.35. Informational finding, does not affect the score.
server: cloudflare x-powered-by: PHP/8.2.35
$ curl -sIL https://mtu.edu/ | grep -iE "^(server|x-powered-by)"
- Hide version numbers in the server settings.
server_tokens off;
Safety: This change is made in your server/CDN settings. Test on staging before production.
DNSSEC — signed DNS records
Needs attention · Severity: Medium · Hardening gap · 0/7The domain's records aren't signed, so in some scenarios users could be redirected to a forged server.
No DS record is published at the parent zone, so there's no DNSSEC chain of trust for this zone.
AD = false DS mtu.edu: NODATA
$ dig +short DS mtu.edu
- Enable DNSSEC at your DNS provider (one click at most providers).
- Copy the DS record your provider generates to your domain registrar.
- Wait for propagation and verify with DNSViz.
dig +dnssec mtu.edu SOA delv mtu.edu
Safety: DNS changes are made only at your DNS provider. This tool only reads public data and changes nothing on the domain. A wrong DS record at the registrar will make the domain stop resolving — copy it exactly from the provider.
CAA — who may issue certificates
Passed · Severity: OK · 5/5Only authorized certificate authorities can issue certificates for the domain.
CAA records: 0 issue "emsign.com" | 0 issue "ssl.com" | 0 issuewild "ssl.com" | 0 issuewild "sectigo.com" | 0 issue "digicert.com" | 0 issue "amazon.com" | 0 issuewild "digicert.com" | 0 issue "letsencrypt.org" | 0 issuewild "letsencrypt.org" | 0 iodef "mailto:security@mtu.edu" | 0 issuewild "emsign.com" | 0 issue "godaddy.com" | 0 issue "globalsign.com" | 0 issue "sectigo.com"
0 issue "emsign.com" 0 issue "ssl.com" 0 issuewild "ssl.com" 0 issuewild "sectigo.com" 0 issue "digicert.com" 0 issue "amazon.com" 0 issuewild "digicert.com" 0 issue "letsencrypt.org" 0 issuewild "letsencrypt.org" 0 iodef "mailto:security@mtu.edu" 0 issuewild "emsign.com" 0 issue "godaddy.com" 0 issue "globalsign.com" 0 issue "sectigo.com"
$ dig +short CAA mtu.edu
DNS server redundancy
Passed · Severity: OK · 3/3The domain is served by several DNS servers, so one server failing won't take it down.
5 NS servers.
dns3.merit.net dns1.merit.net dns.mtu.edu dns2.mtu.edu dns2.merit.net
$ dig +short NS mtu.edu
Indicative alignment
Best-practice mapping of public findings to common frameworks. Passive scanning tests public configuration only; it doesn't prove compliance or a violation.
- Google & Yahoo sender rules1 observed gaps
- PCI DSS v4.02 observed gaps
- NIS2 / vendor due diligence3 observed gaps
- SOC 2 / ISO 27001 baseline5 observed gaps
Indicative alignment only, based on public configuration. It doesn't establish whether a framework applies to you, and it isn't legal advice, an audit or a certification.
Public DNS records
| A | mtu.edu | 141.219.70.117 |
| AAAA | mtu.edu | — |
| MX | mtu.edu | 1 aspmx.l.google.com | 10 aspmx2.googlemail.com | 5 alt2.aspmx.l.google.com | 5 alt1.aspmx.l.google.com | 10 aspmx3.googlemail.com |
| NS | mtu.edu | dns3.merit.net | dns1.merit.net | dns.mtu.edu | dns2.mtu.edu | dns2.merit.net |
| TXT | mtu.edu | e2ma-verification=wtveb | e2ma-verification=guveb | e2ma-verification=juveb | google-site-verification=wBIpx8JjuJfOH4oBmX8gtGGdRbSnHHL_LkH6ObknzBs | e2ma-verification=luveb | adobe-idp-site-verification=d1db47eb4cb939d4e965bb06f5ceacd822bc7b3e088fcfe12f3677a18917b380 | e2ma-verification=duveb | DCFBAA7E88A8B23AC6F0C68CC974FBF4 | apple-domain-verification=9TnymFYXDrZtPI4H | hpe-greenlake-domain-verification=4f3961437a6a6f57703350625352734436587364526f6f704c68474e3032582d | e2ma-verification=d4zcb | e2ma-verification=duvet | e2ma-verification=5gpeb | v=spf1 ip4:141.219.0.0/16 include:secure.giftlegacy.com include:_spf.google.com include:emailsrvr.com include:e2ma.net include:spf.watermarkinsights.com ip4:209.61.151.0/24 ip4:166.78.68.0/22 ip4:198.61.254.0/23 ip4:192.237.158.0/23 ip4:23.253.182.0/23 ip4:104.130.96.0/28 ip4:146.20.113.0/24 ip4:146.20.191.0/24 ip4:159.135.224.0/20 ip4:69.72.32.0/20 ip4:104.130.122.0/23 ip4:146.20.112.0/26 ip4:161.38.192.0/20 ip4:143.55.224.0/21 ip4:143.55.232.0/22 ip4:159.112.240.0/20 ip4:198.244.48.0/20 ip4:204.220.168.0/21 ip4:204.220.176.0/20 ip4:38.106.32.22/32 ip4:38.106.32.46/32 ip4:54.240.121.247 ip4:54.240.121.248 ip4:103.237.104.0/22 ip4:104.47.0.0/17 ip4:13.111.0.0/20 ip4:132.174.100.123 ip4:132.174.100.127 ip4:132.174.100.128 ip4:132.174.100.129 ip4:132.174.129.13 ip4:132.174.29.192/27 ip4:134.170.132.0/24 ip4:134.170.140.0/24 ip4:136.146.128.64/27 ip4:136.146.208.16/28 ip4:136.146.210.16/28 ip4:136.147.128.0/20 ip4:136.147.176.0/20 ip4:136.147.182.0/24 ip4:136.147.46.192/26 ip4:136.147.62.192/26 ip4:139.146.146.128/25 ip4:139.146.160.0/25 ip4:157.55.133.0/25 ip4:157.55.158.0/23 ip4:157.55.234.0/24 ip4:157.56.110.0/23 ip4:157.56.112.0/24 ip4:157.56.116.0/25 ip4:157.56.120.0/25 ip4:157.56.87.192/26 ip4:162.247.216.0/22 ip4:167.89.0.0/17 ip4:173.193.132.0/23 ip4:173.203.2.0/25 ip4:173.203.6.0/23 ip4:174.137.46.0/24 ip4:174.36.80.208/28 ip4:174.36.84.12 ip4:174.36.84.14/31 ip4:174.36.84.245 ip4:174.36.84.32 ip4:174.36.92.96/27 ip4:182.50.78.64/28 ip4:185.12.80.0/22 ip4:185.28.196.0/22 ip4:188.172.128.0/20 ip4:192.161.144.0/20 ip4:192.254.112.0/20 ip4:192.28.128.0/18 ip4:192.41.76.4 ip4:192.41.90.128/26 ip4:192.87.104.130 ip4:192.87.44.30 ip4:193.240.184.6 ip4:193.240.184.7 ip4:198.137.189.11 ip4:198.137.190.123 ip4:198.187.195.89 ip4:198.187.196.0/24 ip4:198.21.0.0/21 ip4:198.245.80.0/20 ip4:198.37.144.0/20 ip4:199.106.139.112/28 ip4:199.122.120.0/21 ip4:199.15.212.0/22 ip4:199.244.78.223 ip4:199.244.78.224 ip4:199.91.136.26 ip4:199.91.136.28 ip4:199.91.140.26 ip4:204.14.232.64/28 ip4:204.14.234.64/28 ip4:204.14.238.0/27 ip4:206.107.42.254 ip4:206.152.1.94 ip4:206.79.10.196 ip4:207.126.144.0/20 ip4:207.250.68.0/24 ip4:207.46.100.0/24 ip4:207.46.101.128/26 ip4:207.46.108.0/25 ip4:207.46.163.0/24 ip4:207.46.51.64/26 ip4:207.67.38.0/24 ip4:207.67.98.192/27 ip4:208.117.48.0/20 ip4:208.43.21.28 ip4:208.43.21.66 ip4:208.43.21.70 ip4:209.43.22.0/28 ip4:213.199.154.0/24 ip4:213.199.180.0/24 ip4:213.212.88.171 ip4:216.138.238.192/26 ip4:216.146.46.10 ip4:216.146.46.11 ip4:216.151.85.132 ip4:216.151.85.133 ip4:216.198.0.0/18 ip4:216.32.180.0/23 ip4:217.199.180.36 ip4:23.103.128.0/19 ip4:23.103.191.0/24 ip4:23.103.198.0/23 ip4:23.103.200.0/21 ip4:23.103.208.0/21 ip4:23.229.217.108 ip4:27.111.242.222 ip4:37.188.97.188/32 ip4:40.107.0.0/16 ip4:50.31.32.0/19 ip4:50.57.0.0/27 ip4:52.2.127.126 ip4:52.2.36.135 ip4:59.167.34.100 ip4:62.204.93.131 ip4:63.146.161.230 ip4:64.106.241.148 ip4:64.132.88.0/23 ip4:64.132.92.0/24 ip4:64.18.0.0/20 ip4:64.4.22.64/26 ip4:64.72.147.0/24 ip4:65.55.169.0/24 ip4:65.55.88.0/24 ip4:66.150.160.0/24 ip4:66.18.116.43 ip4:66.231.80.0/20 ip4:66.35.37.96/27 ip4:67.192.241.0/24 ip4:67.228.21.188 ip4:67.228.50.32/27 ip4:68.232.192.0/20 ip4:69.164.120.70 ip4:72.3.185.0/24 ip4:72.32.154.0/24 ip4:72.32.217.0/24 ip4:72.32.243.0/24 ip4:74.115.207.202 ip4:74.115.207.212 ip4:74.115.207.213 ip4:74.206.109.32/27 ip4:74.62.122.128/28 ip4:74.86.113.29 ip4:74.86.207.39 ip4:74.86.236.242 ip4:74.86.241.250 ip4:75.126.200.128/27 ip4:75.126.253.0/24 ip4:80.150.125.180 ip4:80.150.125.181 ip4:85.17.187.195 ip4:85.222.130.192/26 ip4:85.222.138.192/26 ip4:94.236.119.0/26 ip4:95.211.74.199 ip4:96.43.144.64/28 ip4:96.43.147.64/28 ip4:96.43.148.64/28 ip4:96.43.151.64/28 ip4:96.43.152.64/27 ip4:96.43.153.64/27 ip4:96.46.150.192/27 ip4:98.129.184.0/23 ip4:74.122.104.0/22 ip4:72.50.228.0/24 ip4:69.32.224.120/30 ip4:54.240.57.46/31 ip4:159.135.238.30/32 ip4:204.220.188.71/32 ip4:204.220.188.72/30 ip6:2607:f8b0:400c:c10::1b ip6:2800:3f0:4003:c01::1b ip6:2a01:111:f400::/48 ip6:2a04:35c0::/29 ~all | e2ma-verification=c4zcb | e2ma-verification=hd0fb | google-site-verification=_AZlprY5eM4Vq-CEZYqi5Vdijf5ACXlgjUcmaZO44NU | amazonses:KUSt0CCDJKsqh3o9tzCqLjbQgUB5R2qu9M0Y181h744= | e2ma-verification=kuveb | MS=ms79839354 | atlassian-domain-verification=2qCpeFuaK61/oMB9pXnozR19mgu8KbyNdwprWPvmWgxYfnvg5VksFJrI1oZX/90D |
| TXT | _dmarc.mtu.edu | v=DMARC1; p=none; ruf=mailto:michigantechit@us.cp-dmarc.com; rua=mailto:michigantechit@us.cp-dmarc.com,mailto:2hzorv7s@ag.us.dmarcian.com,mailto:dmarc-report-l@mtu.edu |
| CAA | mtu.edu | 0 issue "emsign.com" | 0 issue "ssl.com" | 0 issuewild "ssl.com" | 0 issuewild "sectigo.com" | 0 issue "digicert.com" | 0 issue "amazon.com" | 0 issuewild "digicert.com" | 0 issue "letsencrypt.org" | 0 issuewild "letsencrypt.org" | 0 iodef "mailto:security@mtu.edu" | 0 issuewild "emsign.com" | 0 issue "godaddy.com" | 0 issue "globalsign.com" | 0 issue "sectigo.com" |
| DS | mtu.edu | — |