Skip to content
https://dictionary.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
0
REVIEW
4
PASS
5
INFO
0
Probed from Singapore, Singapore
301 Moved Permanently
Checks
9
5 PASS 4 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
42 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable DNSSEC on your domain for DNS spoofing protection
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
B
CDN & Delivery
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: SIN)
Got: cf-ray: 9efee87b6d76fe8c-SIN
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9efee87b6d76fe8c-SIN
A
DNS Records
2 A records, 588 ms lookup
PASS
2 A records, 588 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 172.64.145.130, 104.18.42.126
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1219.awsdns-24.org, ns-1699.awsdns-20.co.uk, ns-470.awsdns-58.com, ns-565.awsdns-06.net
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 (588 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 588 ms
A172.64.145.130, 104.18.42.126
AAAA
CNAME
NSns-1219.awsdns-24.org, ns-1699.awsdns-20.co.uk, ns-470.awsdns-58.com, ns-565.awsdns-06.net
MX
1 mxa.global.inbound.cf-emailsecurity.net
5 mxb.global.inbound.cf-emailsecurity.net
TXT
MS=ms68697777
adobe-idp-site-verification=bb5660f072bd1443b1c089706ebb2e9dcf8db73431873cf4a147...
amazonses:8i1U8t1N1rigg9CpVXvWMeVTizNYEJSFLD5LSvE3HFY=
apple-domain-verification=ghP-ikbtzFUfEulaIubBman0WWpHTrFl2Y03SCLI8S4
atlassian-domain-verification=0yhisrId0Tamjg4e1r/KW1MbNjqCvFZrMGM9auACMX/0arIc0m...
atlassian-domain-verification=uUTQHYge655RxaiCqp-IAyc/Q7GgtoJziDouyp0rB7n8OUdp4q...
cb4v9d18m504rj2m7wwszq439jpf91b8
docusign=df9eb68e-8f31-4a70-a89a-efbdaa16f096
facebook-domain-verification=k6l24sw20l3wqqhhdj5pmmkmgv7c5s
google-site-verification=8yftWgkHXwwEIAgGd_QO_ojsLMx3uCcjw_hxycnwb6w
google-site-verification=A6Q6nJTZslHyjfgzJplMgswuMVGwMHa-bDvo6gqS6R0
google-site-verification=Ad3F7HWoONZsYEmQ1XS2_ilCcBs0QdN-GSh1RA6n0iA
google-site-verification=Dglp1g8zU22QHe5Cw223GFcsf-WAKLd4G6BuYPf179A
google-site-verification=MCrg9tYx-LGFk3mdXdLa8k2caJuAi9PyCO_Ihrco96E
google-site-verification=i1knPoCggWbYbqbiSuwExGFugPZUinxrtgirusfusoU
google-site-verification=sAKU3njtuEOKB8IuaVMl4nNJa5PcaVIgYqPhrxelGqM
google-site-verification=ujm3OGg8fiKGqxo4Rj_OIoMuqolTbSyl7VvokaxRL5Y
google-site-verification=ulC57vmeyKqUw0FzW6s-SqkzWeBMixcoqCGuIYePffc
google-site-verification=wdkKQExbGsEWMeDDdDjuJct8oLDEy9tyzpiXYNEhW2M
mongodb-site-verification=YDAIxbJk9qi4S1JxpRsejHnuq0NTjo2x
onetrust-domain-verification=3a0b28362d3a4116b4218c8ec36a71a2
SPF v=spf1 redirect=dictionary.com.hosted.spf-report.com
yahoo-verification-key=IjpAp7GpT1iDFeUsPVZ2xCU4b49tiyhBdeRVuSYhnuA=
CAALookup not available with standard resolver
Resolved in 588 ms

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), 237 ms total
PASS
1 redirect(s), 237 ms total
Info::
Single redirect
Got: https://dictionary.com → https://www.dictionary.com/ (301)
Info::
WWW normalization redirect

https://dictionary.com

120 ms · HTTP/1.1

301

https://www.dictionary.com/

117 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://dictionary.com301120 msHTTP/1.1cloudflare
2https://www.dictionary.com/403117 msHTTP/1.1cloudflare

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.dictionary.com/
200https://dictionary.com/

HTTP → HTTPS

301http://dictionary.com/ https://dictionary.com/

Consistent

A+
Domain Intelligence
dictionary.com — via 101domain GRS Limited, 31 years, 4 months old, hosted on Cloudflare
PASS
dictionary.com — via 101domain GRS Limited, 31 years, 4 months old, hosted on Cloudflare
Info::
Domain registered until May 15, 2027 (1 years remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: 101domain GRS Limited
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: Cloudflare
Got: AS13335
Domain expiry

271 days

May 15, 2027

SSL certificate

42 days

Issued by Google Trust Services

Domain age

31 years, 4 months

Registered May 14, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

104.18.42.126

Registrar

101domain GRS Limited

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar 101domain GRS Limited
Created May 14, 1995 (31 years, 4 months ago)
Expires May 15, 2027 (1 years)
Last Updated March 16, 2026
Name Servers ns-1219.awsdns-24.org, ns-1699.awsdns-20.co.uk, ns-470.awsdns-58.com, ns-565.awsdns-06.net
DNSSEC Not enabled
Hosting
IP Address 104.18.42.126
ASN AS13335 (CLOUDFLARENET - Cloudflare, Inc., US)
Provider Cloudflare
Data source: rdap (0.4s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

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 113 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
100 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
6 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
114 ms
Total Time Total request time from DNS lookup through full response.
114 ms

Connection waterfall

DNS Lookup 100 ms TCP Connect 1 ms TLS Handshake 6 ms Server Processing 7 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback