Skip to content
https://mitre.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Sao Paulo, Brazil
301 Moved Permanently
Checks
9
6 PASS 3 REVIEW
C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
Crawlability
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
TLS Certificate Expiry & Recommendations
291 days until leaf cert expires — 2 issues to address
REVIEW

Certificate validity

291
days left
0d 30d 60d 90d+

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A
DNS Records
1 A records, 828 ms lookup
PASS
1 A records, 828 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 52.45.20.31
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: dns-ext-mclean.mitre.org, dns-ext-bedford.mitre.org
Info::
2 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Warning::
DNS resolution is slow (828 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 828 ms
A52.45.20.31
AAAA
CNAME
NSdns-ext-mclean.mitre.org, dns-ext-bedford.mitre.org
MX
10 mxb-00007b01.gslb.gpphosted.com
10 mxa-00007b01.gslb.gpphosted.com
TXT
MS=ms20855904
MS=ms98768812
asv=01da61189b941106731e85745beb335c
asv=38e7bda31ceba5cc4900f0ddb0b458d6
apple-domain-verification=IhfpZFDgeQPsl2s6
ibmid:90d8cd03-3154-47c7-a45e-47ad487771a6
google-gws-recovery-domain-verification=46082460
autodesk-domain-verification=-whpSoDCVGlqaNEh9sMu
astro-domain-verification=cm3ise5040nhj01q734ztc1zx
openai-domain-verification=dv-vMiG1XOsOTVIDtSgGFxcip6D
docker-verification=e77c0f46-40d2-4fdf-8503-1c5ee1d3f03c
SPF v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com ~all
cursor-domain-verification-j0jakp=58If2IjXIF2i6OqwGytXYKl9R
facebook-domain-verification=61kpzm6fwx7q0jqi56gwx3jbs7f8p8
anthropic-domain-verification-8hc4ws=pd8VXyhMUVfMofp0MbUT2vIKe
perplexity-ai-domain-verification-87trh2=wtDjepHrRhjhViqjztFRXu5V2
google-site-verification=-CI6a5LJQx644fuYSi_Gv4HUlC-DHLXH6ss6igUca8o
google-site-verification=zxat46-84bBHTt2WJ6OEo7AXFqzllDk1bOnKUE_nDOk
kJ+lU/Y5jVQ5RQ6JmWVOKIWGCXPLAQV2ttbKRWOm0P8yzlblX19OF5PsvuQDgUlUn0NMhhKFLBg52pGb...
infoblox-domain-mastery=9630e11f219a2d74b970d228290a5a75b2483e0688040801c504b91b...
atlassian-domain-verification=BBIEy3hlNwzkj3ARvk5052GdV7wgAzfrh7tZg25p8eNA5q9IXh...
atlassian-domain-verification=IzVqwDmG0yrQMVJFLyEiAJgIKXZhOKbYP3//RBU4h0oQqBXTQk...
CAALookup not available with standard resolver
Resolved in 828 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A
Redirect Chain
1 redirect(s), 794 ms total
PASS
1 redirect(s), 794 ms total
Info::
Single redirect
Got: https://mitre.org → https://www.mitre.org/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 794 ms total
Got: 794 ms

https://mitre.org

616 ms · HTTP/1.1

301

https://www.mitre.org/

178 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://mitre.org301616 msHTTP/1.1nginx
2https://www.mitre.org/403178 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

403https://www.mitre.org/
200https://mitre.org/

HTTP → HTTPS

301http://mitre.org/ https://www.mitre.org/

Consistent

A+
Domain Intelligence
mitre.org — via Network Solutions, LLC, 41 years, 4 months old, hosted on AWS
PASS
mitre.org — via Network Solutions, LLC, 41 years, 4 months old, hosted on AWS
Info::
Domain registered until Jul 9, 2029 (3 years, 3 months remaining)
Info::
DNSSEC is enabled
Info::
Registrar: Network Solutions, LLC
Warning::
Registrar lock is NOT enabled
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Info::
Hosting: AWS
Got: AS14618
Domain expiry

1090 days

July 9, 2029

SSL certificate

291 days

Issued by Sectigo Limited

Domain age

41 years, 4 months

Registered July 10, 1985

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS14618

52.45.20.31

Registrar

Network Solutions, LLC

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Network Solutions, LLC
Created July 10, 1985 (41 years, 4 months ago)
Expires July 9, 2029 (3 years, 3 months)
Last Updated September 16, 2025
Name Servers dns-ext-bedford.mitre.org, dns-ext-mclean.mitre.org
DNSSEC Enabled
Hosting
IP Address 52.45.20.31
ASN AS14618 (AMAZON-AES - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.5s)

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

A
HTTP Probe Timing
Total 614 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
121 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
122 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
248 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
614 ms
Total Time Total request time from DNS lookup through full response.
614 ms

Connection waterfall

DNS Lookup 121 ms TCP Connect 122 ms TLS Handshake 248 ms Server Processing 123 ms Content Transfer 0 ms
A+
CDN & Delivery
Varnish (HIT)
PASS
Varnish (HIT)
Info::
Site is served via Varnish CDN
Got: via: varnish
Info::
CDN cache status: HIT
CDN Detected: Varnish
Provider Varnish Cache Status HIT Evidence via: varnish
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback