Skip to content
https://loremipsum.io

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
0
REVIEW
7
PASS
10
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
10 PASS 7 REVIEW
B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
B
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
No CAA records published
Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.
B
Reverse DNS
0/4 IPs match cert SAN
REVIEW
0/4 IPs match cert SAN
Info::
PTR for 143.204.194.112 does not match any cert SAN: server-143-204-194-112.cdg54.r.cloudfront.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 143.204.194.84 does not match any cert SAN: server-143-204-194-84.cdg54.r.cloudfront.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 143.204.194.126 does not match any cert SAN: server-143-204-194-126.cdg54.r.cloudfront.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 143.204.194.82 does not match any cert SAN: server-143-204-194-82.cdg54.r.cloudfront.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
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
TLS Certificate Expiry & Recommendations
168 days until leaf cert expires — 2 issues to address
REVIEW

Certificate validity

168
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
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.
A+
DNS Records
4 A records, 52 ms lookup
PASS
4 A records, 52 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 143.204.194.112, 143.204.194.84, 143.204.194.126, 143.204.194.82
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1717.awsdns-22.co.uk, ns-1504.awsdns-60.org, ns-718.awsdns-25.net, ns-82.awsdns-10.com
Info::
1 mail exchanger(s) configured
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 52 ms
Got: 52 ms
A143.204.194.112, 143.204.194.84, 143.204.194.126, 143.204.194.82
AAAA—
CNAME—
NSns-1717.awsdns-22.co.uk, ns-1504.awsdns-60.org, ns-718.awsdns-25.net, ns-82.awsdns-10.com
MX
1 smtp.google.com
TXT
google-site-verification=HKChI0Dwe02ayXye-6-SNN7Uy3s5rMShVRRyL68CnY8
CAALookup not available with standard resolver
Resolved in 52 ms

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Multi-Resolver DNS Speed
Mean 30ms across 3 resolvers (spread 18ms)
PASS
Mean 30ms across 3 resolvers (spread 18ms)
Info::
Cloudflare: 21ms
Got: 21ms via 1.1.1.1:53
Info::
Quad9: 31ms
Got: 31ms via 9.9.9.9:53
Info::
Google: 39ms
Got: 39ms via 8.8.8.8:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://loremipsum.io

https://loremipsum.io

58 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://loremipsum.io20058 msHTTP/1.1AmazonS3
A+
Crawlability
robots.txt present, sitemap with 43 URLs
PASS
robots.txt present, sitemap with 43 URLs
Info::
robots.txt is present
Got: 56 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 43 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 56 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Sitemap: https://loremipsum.io/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 43 entries Valid XML Yes
Sample URLs:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

https://www.loremipsum.io/
200https://loremipsum.io/

HTTP → HTTPS

301http://loremipsum.io/ → https://loremipsum.io/

Consistent

A+
Domain Intelligence
loremipsum.io — via NameCheap, Inc., 12 years, 4 months old, hosted on AWS
PASS
loremipsum.io — via NameCheap, Inc., 12 years, 4 months old, hosted on AWS
Info::
Domain registered until Jul 7, 2027 (9 months remaining)
Info::
Registrar: NameCheap, Inc.
Info::
Registrar lock is enabled
Domain cannot be transferred without explicit unlock from the registrar. This protects against unauthorized transfers.
Info::
Hosting: AWS
Got: AS16509
Domain expiry

275 days

July 7, 2027

SSL certificate

168 days

Issued by Amazon

Domain age

12 years, 4 months

Registered July 7, 2014

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

143.204.194.126

Registrar

NameCheap, Inc.

Locked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar NameCheap, Inc.
Created July 7, 2014 (12 years, 4 months ago)
Expires July 7, 2027 (9 months)
Last Updated August 12, 2026
Name Servers ns-1717.awsdns-22.co.uk, ns-718.awsdns-25.net, ns-82.awsdns-10.com, ns-1504.awsdns-60.org
Registrant Privacy service provided by WITHHELD FOR PRIVACY LLC
Hosting
IP Address 143.204.194.126
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: whois (1.5s)

Domain cannot be transferred without explicit unlock from the registrar. This protects against unauthorized transfers.

Why this matters

Registrar lock (clientTransferProhibited et al.) prevents unauthorized domain transfers — strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

A+
HTTP Probe Timing
Total 134 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
47 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.
18 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
100 ms
Total Time Total request time from DNS lookup through full response.
134 ms

Connection waterfall

DNS Lookup 47 ms TCP Connect 16 ms TLS Handshake 18 ms Server Processing 18 ms Content Transfer 34 ms
A+
CDN & Delivery
Document on AWS CloudFront; assets also on Fastly, Cloudflare
PASS
Document on AWS CloudFront; assets also on Fastly, Cloudflare
Info::
Document is served via AWS CloudFront CDN (edge: CDG54-P1)
Got: x-amz-cf-id: 4PAeNcpYTmEp47xX0ZQLrlE0OM3TKs34Cq1l3MQNQovjFteyXyWNTw==
Info::
CDN cache status: Hit from cloudfront
Info::
Assets on Fastly: loremipsum.imgix.net (assets: 9), cache MISS, MISS
Got: delegation dualstack.com.imgix.map.fastly.net
Info::
Assets on Cloudflare: a.pub.network (assets: 4), cache HIT
Got: cf-ray: a4259599798cd10b-CDG
Info::
Assets on AWS CloudFront: cdn.privacy-mgmt.com (assets: 3), cache Hit from cloudfront
Got: x-amz-cf-id: Phe_SJjcwQfbzDhQ623wewLShFxIQhc3Ah2Mvjnbq0NFO5XOtKLXBw==
Document served via CDN: AWS CloudFront
Provider AWS CloudFront Cache Status Hit from cloudfront Evidence x-amz-cf-id: 4PAeNcpYTmEp47xX0ZQLrlE0OM3TKs34Cq1l3MQNQovjFteyXyWNTw==

Asset hosts on a CDN

  • loremipsum.imgix.net — Fastly · assets: 9 · Cache Status: MISS, MISS
  • a.pub.network — Cloudflare · assets: 4 · Cache Status: HIT
  • cdn.privacy-mgmt.com — AWS CloudFront · assets: 3 · Cache Status: Hit from cloudfront

Other asset hosts

  • securepubads.g.doubleclick.net — assets: 2 · below probe threshold
  • www.googletagmanager.com — assets: 1 · below probe threshold
A+
CDN Cache Observability
Cache state: HIT
PASS
Cache state: HIT
Info::
CDN cache state observable via 2 header(s)
Got: age=55084, x-cache=Hit from cloudfront
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback