Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
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
BTLS Certificate Expiry & Recommendations317 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
Recommended actions
- Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
- 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 Records2 A records, 100 ms lookupPASS
| A | 52.223.20.214, 35.71.148.62 |
| AAAA | — |
| CNAME | — |
| NS | ns-1171.awsdns-18.org, ns-18.awsdns-02.com, ns-2009.awsdns-59.co.uk, ns-865.awsdns-44.net |
| MX | 10 aspmx.l.google.com 20 alt1.aspmx.l.google.com 30 alt2.aspmx.l.google.com 40 alt3.aspmx.l.google.com |
| TXT | MS=ms50503649 adobe-idp-site-verification=7d0f6864c606f0fbb47cc6e0221ce184c6fc8e695d2d8ec3051c... facebook-domain-verification=kltje477h0s3g95gkp0my9pgbeors7 google-site-verification=HL1ALA9H13xsTF4VzXnLKP0AvCgkh7zfEvUJS6AD9Ic google-site-verification=iGaxCeN5iv1n3C0e_zFrIjf84lmWqdCxArh2XZVNtho spf2.0/pra a:sopgw.phillynews.com a:exmail4.phillynews.com, ip4:161.188.204.0/24... SPF v=spf1 ip4:161.188.204.0/24 ip4:161.188.211.0/24 ip4:174.132.249.0/24 ip4:64.18.... |
| 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), 784 ms totalPASS
https://philly.com
741 ms · HTTP/1.1
https://www.inquirer.com:443/
43 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://philly.com | 301 | 741 ms | HTTP/1.1 | awselb/2.0 |
| 2 | https://www.inquirer.com:443/ | 200 | 43 ms | HTTP/1.1 | openresty |
See the visual redirect chain in the HTTP Probe tab →
A+Crawlabilityrobots.txt present, sitemap with 86 URLsPASS
User-agent: *
Disallow: /light/
Disallow: /search
Disallow: /sports/betting/
Disallow: /wires/
Disallow: /Preview/
Disallow: /zzz-systest/
Disallow: /zzz_systest/
Disallow: */zzz-systest/
Disallow: */zzz_systest/
Disallow: */zzz_systest/
Sitemap: https://www.inquirer.com/sitemaps/48hour-news-sitemap-partner.xml
Sitemap: https://www.inquirer.com/arc/outboundfeeds/sitemap-index-2/?outputType=xml
Sitemap: https://www.inquirer.com/arc/outboundfeeds/sitemap-restaurant-page/
Sitemap: https://www.inquirer.com/arc/outboundfeeds/sitemap-author-page/
- https://www.inquirer.com/phillies/zack-wheeler-return-start-braves-taijuan-walker-rotation-20260421.html
- https://www.inquirer.com/crime/philly-police-building-vehicle-crash-northeast-20260421.html
- https://www.inquirer.com/soccer/nwsl-expansion-columbus-public-funding-20260421.html
- https://www.inquirer.com/politics/philadelphia/city-council-school-district-closure-uber-tax-parker-20260421.html
- https://www.inquirer.com/news/philadelphia/pew-state-of-city-trends-census-20260421.html
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencephilly.com — via GoDaddy.com, LLC, 28 years, 1 months old, hosted on AWSPASS
1515 days
August 9, 2030
317 days
Issued by Amazon
28 years, 1 months
Registered August 10, 1998
Not enabled
Protects against DNS spoofing
AWS
ASN AS16509
52.223.20.214
GoDaddy.com, LLC
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