Skip to content
https://whatismyipaddress.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
100
GRADE
A+
FIX
0
REVIEW
2
PASS
7
INFO
0
Probed from Madrid, Spain
403 Forbidden
Checks
9
7 PASS 2 REVIEW
B
TLS Certificate Expiry & Recommendations
60 days until leaf cert expires — 2 issues to address
REVIEW

Certificate validity

60
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
B
CDN & Delivery
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: 9f0869a94f5c22a4-CDG
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9f0869a94f5c22a4-CDG
A+
DNS Records
2 A records, 41 ms lookup
PASS
2 A records, 41 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.19.223.79, 104.19.222.79
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700::6813:de4f, 2606:4700::6813:df4f
Info::
2 nameserver(s) configured
Got: simon.ns.cloudflare.com, lucy.ns.cloudflare.com
Info::
5 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
Info::
DNS resolution time: 41 ms
Got: 41 ms
A104.19.223.79, 104.19.222.79
AAAA2606:4700::6813:de4f, 2606:4700::6813:df4f
CNAME—
NSsimon.ns.cloudflare.com, lucy.ns.cloudflare.com
MX
1 aspmx.l.google.com
5 alt2.aspmx.l.google.com
5 alt1.aspmx.l.google.com
10 alt4.aspmx.l.google.com
10 alt3.aspmx.l.google.com
TXT
SPF v=spf1 include:_spf.google.com include:mail.zendesk.com include:servers.mcsv.net...
google-site-verification=Nok-adtb4YRl72yDEbPFnpcsxlRGNrZMAY_l_gLjXvk
facebook-domain-verification=ous0orhakq7n4pknyzmiu1tha9h6r0
google-site-verification=REU8l5064iTxJy-lPUU6jW8W9PTQGUGZeDz1WpJ3s7s
ahrefs-site-verification_025d4503c033da309d088d02b7da6ce0000c757f49cb74da33db5ca...
CAALookup not available with standard resolver
Resolved in 41 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.

A+
Redirect Chain
0 redirect(s), 61 ms total
PASS
0 redirect(s), 61 ms total

https://whatismyipaddress.com

61 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://whatismyipaddress.com40361 msHTTP/1.1cloudflare
A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2606:4700::6813:de4f, 2606:4700::6813:df4f
Got: 17 ms connect
IPv6 Ready
AAAA Records 2606:4700::6813:de4f, 2606:4700::6813:df4f Connection Reachable (17 ms)
A+
Crawlability
robots.txt present, sitemap with 6 URLs
PASS
robots.txt present, sitemap with 6 URLs
Info::
robots.txt is present
Got: 249 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 6 entries
Info::
Sitemap index with 6 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 249 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
Sitemap: https://whatismyipaddress.com/sitemap.xml

User-agent: *
Allow: /ads.txt

User-agent: *
Disallow: /cdn-cgi/
Disallow: /pdf/
Disallow: /wp-admin/
Disallow: /wp-includes/
Disallow: /ds3
Disallow: /search
Disallow: /?s=*
Disallow: /page/*?s=
sitemap.xml 200 OK
Type Sitemap Index URLs 6 entries Valid XML Yes
Child Sitemaps:
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.whatismyipaddress.com/
200https://whatismyipaddress.com/

HTTP → HTTPS

301http://whatismyipaddress.com/ → https://whatismyipaddress.com/

Consistent

A+
Domain Intelligence
whatismyipaddress.com — via GoDaddy.com, LLC, 26 years, 8 months old
PASS
whatismyipaddress.com — via GoDaddy.com, LLC, 26 years, 8 months old
Info::
Domain registered until Jan 4, 2033 (6 years, 9 months remaining)
Info::
DNSSEC is enabled
Info::
Registrar: GoDaddy.com, 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.
Domain expiry

2367 days

January 4, 2033

SSL certificate

60 days

Issued by Google Trust Services

Domain age

26 years, 8 months

Registered January 4, 2000

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700::6813:df4f

Registrar

GoDaddy.com, 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 GoDaddy.com, LLC
Created January 4, 2000 (26 years, 8 months ago)
Expires January 4, 2033 (6 years, 9 months)
Last Updated November 8, 2023
Name Servers lucy.ns.cloudflare.com, simon.ns.cloudflare.com
DNSSEC Enabled
Hosting
IP Address 2606:4700::6813:df4f
Data source: rdap (0.1s)

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

Connection waterfall

DNS Lookup 38 ms TCP Connect 16 ms TLS Handshake 22 ms Server Processing 24 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