Skip to content
https://rubiconproject.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
81
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 3 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
Domain Intelligence
rubiconproject.com — via GoDaddy.com, LLC, 19 years, 2 months old, hosted on SWITCH-LTD - SWITCH, LTD, US
REVIEW
rubiconproject.com — via GoDaddy.com, LLC, 19 years, 2 months old, hosted on SWITCH-LTD - SWITCH, LTD, US
Critical::
Domain expires in 15 days
This domain expires on May 2, 2026. Domains that expire accidentally cause complete website downtime. Enable auto-renewal or renew manually now.
Got: Expires May 2, 2026
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: SWITCH-LTD - SWITCH, LTD, US
Got: AS23005
Domain expiry

EXPIRED

May 2, 2026

SSL certificate

167 days

Issued by DigiCert Inc

Domain age

19 years, 2 months

Registered May 2, 2007

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

SWITCH-LTD - SWITCH, LTD, US

ASN AS23005

69.194.143.123

Registrar

GoDaddy.com, LLC

Unlocked 8 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Domain has EXPIRED — renew immediately to avoid total site outage
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar GoDaddy.com, LLC
Created May 2, 2007 (19 years, 2 months ago)
Expires May 2, 2026 (15 days)
Last Updated May 2, 2025
Name Servers ns-1150.awsdns-15.org, ns-1722.awsdns-23.co.uk, ns-483.awsdns-60.com, ns-644.awsdns-16.net, ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com
DNSSEC Not enabled
Hosting
IP Address 69.194.143.123
ASN AS23005 (SWITCH-LTD - SWITCH, LTD, US)
Provider SWITCH-LTD - SWITCH, LTD, US
Data source: rdap (0.4s)

This domain expires on May 2, 2026. Domains that expire accidentally cause complete website downtime. Enable auto-renewal or renew manually now.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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

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

Certificate validity

167
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
  • 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
1 A records, 38 ms lookup
PASS
1 A records, 38 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 69.194.143.123
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1722.awsdns-23.co.uk, ns-1150.awsdns-15.org, ns-644.awsdns-16.net, ns-483.awsdns-60.com
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: 38 ms
Got: 38 ms
A69.194.143.123
AAAA
CNAME
NSns-1722.awsdns-23.co.uk, ns-1150.awsdns-15.org, ns-644.awsdns-16.net, ns-483.awsdns-60.com
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 aspmx2.googlemail.com
10 aspmx3.googlemail.com
TXT
logmein-domain-confirmation 90DIFG9EEUT8U8R48952255
00d700000008awveam
google-site-verification=U-FUvU0VS4falHBMujbJtZpgqy95I2EFC08ADvrqlSQ
adobe-idp-site-verification=7ba00fd005454fcba9ed31a7ad48786fef98ee97ccc28d469c18...
google-site-verification=8Oe3JXELIVSWdd5P6OY4UM5pF_aqaApPAbdvsIqjvtY
slack-domain-verification=mlIG4ylJounirRIFXuVrwirxvgiAUa63gagbhqV0
SPF v=spf1 ip4:72.34.113.100 ip4:69.194.143.140 include:spf.rubiconproject.com inclu...
docusign=740bb1dc-f7a3-4027-b408-aed4bd2824d0
apple-domain-verification=G4AVkC9r63d1Wgp7
CAALookup not available with standard resolver
Resolved in 38 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

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), 785 ms total
PASS
1 redirect(s), 785 ms total
Info::
Single redirect
Got: https://rubiconproject.com → https://www.magnite.com/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 785 ms total
Got: 785 ms
Info::
Cross-domain redirect detected

https://rubiconproject.com

678 ms · HTTP/1.1

301

https://www.magnite.com/

107 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://rubiconproject.com301678 msHTTP/1.1Apache/2.4.62 (Rocky Linux)
2https://www.magnite.com/403107 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A
Crawlability
robots.txt present, no sitemap
PASS
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 189 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt references sitemap

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

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

robots.txt 200 OK
Size 189 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
Crawl-delay: 10
# START YOAST BLOCK
# ---------------------------
User-agent: *
Disallow:

Sitemap: https://www.magnite.com/sitemap_index.xml
# ---------------------------
# END YOAST BLOCK
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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)
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

301https://www.rubiconproject.com/
200https://rubiconproject.com/

Preferred variant: non-www

HTTP → HTTPS

302http://rubiconproject.com/ https://rubiconproject.com/

Use 301 (permanent) instead of 302 (temporary)

A
HTTP Probe Timing
Total 703 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
28 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
167 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
339 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
703 ms
Total Time Total request time from DNS lookup through full response.
703 ms

Connection waterfall

DNS Lookup 28 ms TCP Connect 167 ms TLS Handshake 339 ms Server Processing 168 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback