Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BCrawlabilityrobots.txt present, no sitemapREVIEW
A sitemap helps search engines discover and index your pages more efficiently.
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
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
User-agent: *
Disallow: /downloadcomp.php
Disallow: /profileinterview.php
Disallow: /pdf_lightbox.php
Disallow: /downloadpubliclightbox.php
Disallow: /mylightbox.php
Disallow: /similar.php
Disallow: /similarmodel_ajax.php
Disallow: /bova/
Disallow: /images/verify_image.png
Disallow: /images/welcome_image.png
Disallow: /images/ga_img_handler.php
Disallow: /bigdata/logging/
Disallow: /visual/
User-agent: GPTBot
Disallow: /
User-agent: Amazonbot
Disallow: /
User-agent: CCBot
Disallow: /
User-agent: anthropic-ai
Disallow: /
User-agent: Claude-Web
Disallow: /
User-agent: Google-Extended
Disallow: /
No sitemap found
Adding a sitemap helps search engines discover your pages.
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations319 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
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
A+DNS Records4 A records, 11 ms lookupPASS
| A | 18.239.36.20, 18.239.36.117, 18.239.36.25, 18.239.36.100 |
| AAAA | — |
| CNAME | — |
| NS | ns-1404.awsdns-47.org, ns-1924.awsdns-48.co.uk, ns-221.awsdns-27.com, ns-562.awsdns-06.net |
| MX | 1 aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com 10 alt4.aspmx.l.google.com 10 alt3.aspmx.l.google.com |
| TXT | google-site-verification=DZbKrto9SwQZ5GIgy5Xis2mKJTCqL6Wd7cbC2KGIoUw google-site-verification=OcmU-t9vdGYOFw7JZqdkaihGKitrLd5Yp3UJ2i0QaPU google-site-verification=SrTyfRBO5DnuePvsjqPtmqnCqL1WAQMWVsSuys_LlUE google-site-verification=b_BMrA0WR5x0xt3PSfQu5cAddhDY32H9MczhzwWt1HE google-site-verification=h2c0kwjDKaCBWUJhbSd7DM22f1fRaZd_qmyuptNZ_SQ google-site-verification=tKHYIrv-hTUoJlXQQyviYg_6nKaNMEzhgqmlX6oJ5zs SPF v=spf1 mx include:_spf.google.com include:sendgrid.net include:mailer.123rf.com ... |
| CAA | Lookup not available with standard resolver |
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
ARedirect Chain1 redirect(s), 768 ms totalPASS
https://123rf.com
462 ms · HTTP/1.1
https://www.123rf.com:443/
306 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://123rf.com | 301 | 462 ms | HTTP/1.1 | awselb/2.0 |
| 2 | https://www.123rf.com:443/ | 200 | 306 ms | HTTP/1.1 |
See the visual redirect chain in the HTTP Probe tab →
A+Domain Intelligence123rf.com — via NameCheap, Inc., 21 years, 5 months old, hosted on AWSPASS
228 days
March 4, 2027
319 days
Issued by Amazon
21 years, 5 months
Registered March 4, 2005
Not enabled
Protects against DNS spoofing
AWS
ASN AS16509
18.239.36.20
NameCheap, Inc.
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
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.
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