Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BRedirect Chain1 redirect(s), 1058 ms totalREVIEW
https://niemanlab.org
1017 ms · HTTP/1.1
https://www.niemanlab.org/
41 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://niemanlab.org | 301 | 1017 ms | HTTP/1.1 | cloudflare |
| 2 | https://www.niemanlab.org/ | 200 | 41 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BHTTP Probe TimingTotal 1074 ms — DNS, TCP, TLS, TTFB, content transfer breakdownREVIEW
Connection waterfall
BTLS Certificate Expiry & Recommendations56 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 Records3 A records, 39 ms lookupPASS
| A | 104.26.8.173, 172.67.68.133, 104.26.9.173 |
| AAAA | 2606:4700:20::ac43:4485, 2606:4700:20::681a:9ad, 2606:4700:20::681a:8ad |
| CNAME | — |
| NS | jaime.ns.cloudflare.com, vivienne.ns.cloudflare.com |
| MX | 50 qs2789.pair.com |
| TXT | SPF v=spf1 include:amazonses.com ~all |
| 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.
A+IPv6 ReadinessIPv6 reachable (1 ms)PASS
A+Crawlabilityrobots.txt present, sitemap with 14 URLsPASS
User-agent: Slurp
Disallow: /
User-agent: Yahoo! Slurp
Disallow: /
# Block wiederfreibot as it is just noise
User-agent: wiederfreibot/1.0
Disallow: /
# Block CazoodleBot as it does not present correct accept content headers
User-agent: CazoodleBot
Disallow: /
# Block MJ12bot as it is just noise
User-agent: MJ12bot
Disallow: /
# Block dotbot as it cannot parse base urls properly
User-agent: dotbot/1.0
Disallow: /
# Block Gigabot
User-agent: Gigabot
Disallow: /
# Block AhrefsBot
User-agent: AhrefsBot
Disallow: /
# Block YandexBot
User-agent: YandexBot
Disallow: /
# Block Yandex
User-agent: Yandex
Disallow: /
# Block Exabot
User-agent: Exabot
Disallow: /
# Block PathDefender
User-agent: PathDefender
Disallow: /
# Block Goodzer
User-agent: Goodzer
Disallow: /
# Block MegaIndex.ru
User-agent: MegaIndex.ru/2.0
Disallow: /
# Block Ezooms
User-agent: Ezooms
Disallow: /
# Block Baiduspider
User-agent: Baiduspider
Disallow: /
User-agent: MJ12bot
Disallow: /
User-agent: Vagabondo
Disallow: /
User-agent: Yandex
Disallow: /
User-agent: BSpider
Disallow: /
# Block common cralwers:
User-agent: voltron
Disallow: /
# Some weird backlink checker (webmeup.com)
User-agent: BLEXBot
Disallow: /
# Another backlink crawler
User-agent: linkdexbot/2.0
Disallow: /
# Another backlink crawler (https://ahrefs.com/robot)
User-Agent: AhrefsBot
Disallow: /
# Another one.
User-Agent: GetintentCrawler
Disallow: /
User-agent: Cliqzbot
Disallow: /
User-agent: MJ12bot
Disallow: /
User-agent: Mail.RU_Bot
Disallow: /
User-agent: OSG_BOT
Disallow: /
User-agent: VegeBot
Disallow: /
Crawl-delay: 60
User-agent: "Vegi bot (we follow your robots.txt settings before crawling, you can slow down the bot by change the Crawl-Delay parameter in the settings.if you have an enquiry, please email to: abuse-report@terrykyleseoagency.com)"
Disallow: /
Crawl-delay: 60
User-agent: adbeat_bot
Disallow: /
User-agent: Jooblebot
Disallow: /
# BEGIN W3TC ROBOTS
User-agent: *
Disallow: /wp-content/cache/
# END W3TC ROBOTS
Sitemap: https://www.niemanlab.org/sitemap.xml
- https://www.niemanlab.org/sitemap-misc.x...
- https://www.niemanlab.org/post-sitemap.x...
- https://www.niemanlab.org/post-sitemap2....
- https://www.niemanlab.org/post-sitemap3....
- https://www.niemanlab.org/post-sitemap4....
- https://www.niemanlab.org/post-sitemap5....
- https://www.niemanlab.org/post-sitemap6....
- https://www.niemanlab.org/post-sitemap7....
- https://www.niemanlab.org/post-sitemap8....
- https://www.niemanlab.org/post-sitemap9....
- https://www.niemanlab.org/post-sitemap10...
- https://www.niemanlab.org/post-sitemap11...
- https://www.niemanlab.org/post-sitemap12...
- https://www.niemanlab.org/page-sitemap.x...
A+Domain Intelligenceniemanlab.org — via pair Networks, Inc. d/b/a pair Domains, 17 years, 11 months oldPASS
29 days
August 11, 2026
56 days
Issued by Google Trust Services
17 years, 11 months
Registered August 11, 2008
Not enabled
Protects against DNS spoofing
Unknown
2606:4700:20::681a:9ad
pair Networks, Inc. d/b/a pair Domains
Expiry timeline
Recommended actions
- Renew the domain or enable auto-renewal to prevent accidental expiry
- 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