Skip to content
https://spokesman.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
93
GRADE
A
FIX
0
REVIEW
2
PASS
7
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
7 PASS 2 REVIEW
B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.spokesman.com/
200https://spokesman.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

B
TLS Certificate Expiry & Recommendations
175 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

175
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
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+
DNS Records
4 A records, 55 ms lookup
PASS
4 A records, 55 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 108.157.113.44, 108.157.113.50, 108.157.113.96, 108.157.113.124
Info::
Has 8 IPv6 (AAAA) record(s)
Got: 2600:9000:237f:3c00:13:3ce1:5800:93a1, 2600:9000:237f:600:13:3ce1:5800:93a1, 2600:9000:237f:5000:13:3ce1:5800:93a1, 2600:9000:237f:9800:13:3ce1:5800:93a1, 2600:9000:237f:f800:13:3ce1:5800:93a1, 2600:9000:237f:4400:13:3ce1:5800:93a1, 2600:9000:237f:7400:13:3ce1:5800:93a1, 2600:9000:237f:be00:13:3ce1:5800:93a1
Info::
4 nameserver(s) configured
Got: ns-371.awsdns-46.com, ns-898.awsdns-48.net, ns-1860.awsdns-40.co.uk, ns-1144.awsdns-15.org
Info::
1 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: 55 ms
Got: 55 ms
A108.157.113.44, 108.157.113.50, 108.157.113.96, 108.157.113.124
AAAA2600:9000:237f:3c00:13:3ce1:5800:93a1, 2600:9000:237f:600:13:3ce1:5800:93a1, 2600:9000:237f:5000:13:3ce1:5800:93a1, 2600:9000:237f:9800:13:3ce1:5800:93a1, 2600:9000:237f:f800:13:3ce1:5800:93a1, 2600:9000:237f:4400:13:3ce1:5800:93a1, 2600:9000:237f:7400:13:3ce1:5800:93a1, 2600:9000:237f:be00:13:3ce1:5800:93a1
CNAME—
NSns-371.awsdns-46.com, ns-898.awsdns-48.net, ns-1860.awsdns-40.co.uk, ns-1144.awsdns-15.org
MX
10 spokesman-com.mail.protection.outlook.com
TXT
globalsign-domain-verification=4708AB27038FD0C47E4DAE9583E975FC
MS=ms33546368
google-site-verification=aFAahFN1lOMUBV1SE1vFSpixD5QUUcnTvO21Mu_zG2I
apple-domain-verification=wYyRo8QP666zorq6
em7e9r9h8ikicdlq8vjd984elg
oedcbjovu8mtcp47of4epifd6p
SPF v=spf1 mx ip4:52.6.112.187 ip4:50.212.195.242 ip4:4.16.175.46 ip4:4.17.251.250 i...
facebook-domain-verification=b8fdvwzwz5rmijb84e5c0x1p6ly4nz
shldoegq773k6iuajatqubnjt6
CAALookup not available with standard resolver
Resolved in 55 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
1 redirect(s), 368 ms total
PASS
1 redirect(s), 368 ms total
Info::
Single redirect
Got: https://spokesman.com → https://www.spokesman.com/ (301)
Info::
WWW normalization redirect

https://spokesman.com

33 ms · HTTP/1.1

301

https://www.spokesman.com/

335 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://spokesman.com30133 msHTTP/1.1AmazonS3
2https://www.spokesman.com/200335 msHTTP/1.1nginx/1.30.0

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (1 ms)
PASS
IPv6 reachable (1 ms)
Info::
IPv6 is configured and reachable at 2600:9000:237f:3c00:13:3ce1:5800:93a1, 2600:9000:237f:600:13:3ce1:5800:93a1, 2600:9000:237f:5000:13:3ce1:5800:93a1, 2600:9000:237f:9800:13:3ce1:5800:93a1, 2600:9000:237f:f800:13:3ce1:5800:93a1, 2600:9000:237f:4400:13:3ce1:5800:93a1, 2600:9000:237f:7400:13:3ce1:5800:93a1, 2600:9000:237f:be00:13:3ce1:5800:93a1
Got: 1 ms connect
IPv6 Ready
AAAA Records 2600:9000:237f:3c00:13:3ce1:5800:93a1, 2600:9000:237f:600:13:3ce1:5800:93a1, 2600:9000:237f:5000:13:3ce1:5800:93a1, 2600:9000:237f:9800:13:3ce1:5800:93a1, 2600:9000:237f:f800:13:3ce1:5800:93a1, 2600:9000:237f:4400:13:3ce1:5800:93a1, 2600:9000:237f:7400:13:3ce1:5800:93a1, 2600:9000:237f:be00:13:3ce1:5800:93a1 Connection Reachable (1 ms)
A+
Crawlability
robots.txt present, sitemap with 1140 URLs
PASS
robots.txt present, sitemap with 1140 URLs
Info::
robots.txt is present
Got: 1340 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 1140 entries
Info::
Sitemap index with 1140 child sitemaps
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 1340 B Sitemaps referenced 0 User-agents *, bingbot, TurnitinBot, Baiduspider, Twitterbot Blocking No — crawling allowed
# 2019-03-28
User-agent: *
Crawl-delay: 10
Disallow: /accounts/
Disallow: /blockemail/
Disallow: /circ/
Disallow: /comments/
Disallow: /contact/
Disallow: /credit/
Disallow: /customer-comment-form/
Disallow: /digitalcredit/
Disallow: /email/
Disallow: /fragment/
Allow: /newsletters/$
Disallow: /newsletters/
Disallow: /newstart/
Disallow: /profiles/
Disallow: /search/
Disallow: /share/
Disallow: /sradmin/
Disallow: /tags/
Disallow: /xml/
#Disallow: /*?

User-agent: bingbot
Disallow: /accounts/
Disallow: /circ/
Disallow: /comments/
Disallow: /contact/
Disallow: /credit/
Disallow: /customer-comment-form/
Disallow: /digitalcredit/
Disallow: /email/
Disallow: /fragment/
Allow: /newsletters/$
Disallow: /newsletters/
Disallow: /newstart/
Disallow: /profiles/
Disallow: /search/
Disallow: /share/
Disallow: /sradmin/
Disallow: /tags/
Disallow: /xml/
#Disallow: /*?

User-agent: TurnitinBot
Disallow: /

User-agent: Baiduspider
Disallow: /

User-agent: Twitterbot
Disallow: /accounts/
Disallow: /circ/
Disallow: /comments/
Disallow: /contact/
Disallow: /credit/
Disallow: /customer-comment-form/
Disallow: /digitalcredit/
Disallow: /email/
Disallow: /fragment/
Allow: /newsletters/$
Disallow: /newsletters/
Disallow: /newstart/
Disallow: /profiles/
Disallow: /search/
Disallow: /share/
Disallow: /sradmin/
Disallow: /tags/
Disallow: /xml/
sitemap.xml 200 OK
Type Sitemap Index URLs 1140 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
spokesman.com — via Network Solutions, LLC, 31 years, 8 months old
PASS
spokesman.com — via Network Solutions, LLC, 31 years, 8 months old
Info::
Domain registered until Jan 8, 2030 (3 years, 9 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: Network Solutions, 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

1274 days

January 8, 2030

SSL certificate

175 days

Issued by Amazon

Domain age

31 years, 8 months

Registered January 9, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2600:9000:237f:4400:13:3ce1:5800:93a1

Registrar

Network Solutions, LLC

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Network Solutions, LLC
Created January 9, 1995 (31 years, 8 months ago)
Expires January 8, 2030 (3 years, 9 months)
Last Updated November 9, 2024
Name Servers ns-1144.awsdns-15.org, ns-1860.awsdns-40.co.uk, ns-371.awsdns-46.com, ns-898.awsdns-48.net
DNSSEC Not enabled
Hosting
IP Address 2600:9000:237f:4400:13:3ce1:5800:93a1
Data source: rdap (0.1s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

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.

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

Connection waterfall

DNS Lookup 68 ms TCP Connect 1 ms TLS Handshake 4 ms Server Processing 302 ms Content Transfer 0 ms
A
CDN & Delivery
AWS CloudFront (Miss from cloudfront)
PASS
AWS CloudFront (Miss from cloudfront)
Info::
Site is served via AWS CloudFront CDN (edge: MAD56-P2)
Got: x-amz-cf-id: OeMD67I4MQO7alVTpWO1hISDbrzyBYaEbylJ2LHW3vQfApElPfnS_Q==
Info::
CDN cache status: Miss from cloudfront
CDN Detected: AWS CloudFront
Provider AWS CloudFront Cache Status Miss from cloudfront Evidence x-amz-cf-id: OeMD67I4MQO7alVTpWO1hISDbrzyBYaEbylJ2LHW3vQfApElPfnS_Q==
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback