Skip to content
https://runsignup.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
93
GRADE
A
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from New York, United Stated
200 OK
Checks
9
6 PASS 2 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

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
64 days until leaf cert expires — 6 issues to address
REVIEW

Certificate validity

64
days left
0d 30d 60d 90d+

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • Add includeSubDomains to the HSTS directive
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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
3 A records, 6 ms lookup
PASS
3 A records, 6 ms lookup
Info::
Resolves to 3 IPv4 address(es)
Got: 34.194.61.140, 54.165.155.11, 3.222.216.205
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1110.awsdns-10.org, ns-2028.awsdns-61.co.uk, ns-354.awsdns-44.com, ns-652.awsdns-17.net
Info::
5 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: 6 ms
Got: 6 ms
A34.194.61.140, 54.165.155.11, 3.222.216.205
AAAA—
CNAME—
NSns-1110.awsdns-10.org, ns-2028.awsdns-61.co.uk, ns-354.awsdns-44.com, ns-652.awsdns-17.net
MX
10 aspmx.l.google.com
15 alt1.aspmx.l.google.com
15 alt2.aspmx.l.google.com
20 aspmx3.googlemail.com
20 aspmx2.googlemail.com
TXT
google-site-verification=dsfht969bnZxcg1-JPzoWkjY3feA1nd69gAexWobDlQ
google-site-verification=wFyq2zuG7IBY5ilQqEELBypyn04UZIYBgKPHrTMnTUg
SPF v=spf1 include:_spf.google.com include:amazonses.com include:sendgrid.net includ...
yahoo-verification-key=HLCWHKsGl5wdF1PSi0an5kSJSaxo8Xnd2luAMg6Mn6c=
CAALookup not available with standard resolver
Resolved in 6 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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://runsignup.com

https://runsignup.com

56 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://runsignup.com20056 msHTTP/1.1nginx
A+
Crawlability
robots.txt present, sitemap with 21 URLs
PASS
robots.txt present, sitemap with 21 URLs
Info::
robots.txt is present
Got: 1450 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 21 entries
Info::
Sitemap index with 21 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1450 B Sitemaps referenced 1 User-agents SemrushBot, BLEXBot, AhrefsBot, YandexBot, SemrushBot-SA, VegeBot, PiplBot, facebookexternalhit, dotbot, AlphaSeoBot, *, Vegi bot, BaiduSpider, panscient.com, PetalBot Blocking No — crawling allowed
Sitemap: https://runsignup.com/sitemap.xml

User-agent: YandexBot
Disallow: /

User-agent: dotbot
Disallow: /

User-agent: SemrushBot
Disallow: /

User-agent: SemrushBot-SA
Disallow: /

User-agent: VegeBot
Disallow: /

User-agent: Vegi bot
Disallow: /

User-agent: BaiduSpider
Disallow: /

User-agent: BLEXBot
Disallow: /

User-agent: panscient.com
Disallow: /

User-agent: AhrefsBot
Disallow: /

User-agent: PiplBot
Disallow: /

User-agent: AlphaSeoBot
Disallow: /

User-agent: PetalBot
Disallow: /

User-agent: facebookexternalhit
Allow: /Race/Photos/ViewPhoto/

User-agent: *
Disallow: /Race/NJ/Moorestown/InYourFaceScrapper
Disallow: /race/nj/moorestown/inyourfacescrapper
Disallow: /Race/FindARunner/
Disallow: /captcha
Disallow: /em/
Disallow: /Logout
Disallow: /wp-login.php
Disallow: /wp-admin/
Disallow: /wp-content/
Disallow: /wp-includes/
Disallow: /Race/Photos/ViewPhoto/
Disallow: /Race/Results/Simple/
# Place wildcards last since some robots don't know how to parse them
Disallow: /Race/Public/Certificates/*
Disallow: /Race/Results/*/FinishersCert
Disallow: /Race/Results/*/FinishersCertImg
Disallow: /Race/Results/*/RaceDayPhotos
Disallow: /Race/Results/*?customResultsPageId=
Disallow: /*?*PHPSESSID*
Disallow: /*?*embedId2*
Disallow: /*?*embedToken*
Disallow: /*?*regToken*
Disallow: /*?*RefCode=*
Disallow: /*?*err=*
Disallow: /*?*smsg=*
Disallow: /*?*redirect=*
Disallow: /*?*autoLogin*
Disallow: /*?*remMeAttempt*
Crawl-delay: 1
sitemap.xml 200 OK
Type Sitemap Index URLs 21 entries Valid XML Yes
Child Sitemaps:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

302https://www.runsignup.com/
200https://runsignup.com/

Preferred variant: non-www

HTTP → HTTPS

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

Consistent

A+
Domain Intelligence
runsignup.com — via GoDaddy.com, LLC, 17 years, 1 months old, hosted on AWS
PASS
runsignup.com — via GoDaddy.com, LLC, 17 years, 1 months old, hosted on AWS
Info::
Domain registered until Jun 11, 2027 (1 years, 1 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: GoDaddy.com, 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.
Info::
Hosting: AWS
Got: AS14618
Domain expiry

361 days

June 11, 2027

SSL certificate

64 days

Issued by Let's Encrypt

Domain age

17 years, 1 months

Registered June 11, 2009

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS14618

54.165.155.11

Registrar

GoDaddy.com, 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 GoDaddy.com, LLC
Created June 11, 2009 (17 years, 1 months ago)
Expires June 11, 2027 (1 years, 1 months)
Last Updated June 12, 2025
Name Servers ns-1110.awsdns-10.org, ns-2028.awsdns-61.co.uk, ns-354.awsdns-44.com, ns-652.awsdns-17.net
DNSSEC Not enabled
Hosting
IP Address 54.165.155.11
ASN AS14618 (AMAZON-AES - Amazon.com, Inc., US)
Provider AWS
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 62 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
3 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
7 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
19 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
62 ms
Total Time Total request time from DNS lookup through full response.
63 ms

Connection waterfall

DNS Lookup 3 ms TCP Connect 7 ms TLS Handshake 19 ms Server Processing 33 ms Content Transfer 1 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback