Skip to content
https://yieldmo.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
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
86 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

86
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
1 A records, 5 ms lookup
PASS
1 A records, 5 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 35.212.43.67
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-1326.awsdns-37.org, ns-146.awsdns-18.com, ns-2030.awsdns-61.co.uk, ns-635.awsdns-15.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: 5 ms
Got: 5 ms
A35.212.43.67
AAAA
CNAME
NSns-1326.awsdns-37.org, ns-146.awsdns-18.com, ns-2030.awsdns-61.co.uk, ns-635.awsdns-15.net
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 aspmx3.googlemail.com
10 aspmx2.googlemail.com
TXT
ZOOM_verify_FddIs7V7yi7LjpttVnchTx
apple-domain-verification=KMIcmya8S74IvhAN
as=1651826319
google-site-verification=EMMdKgJBKeh-O5deTmY-E47ddK5_gxLP8WgE6xYrNDY
google-site-verification=Nc-farRVYlDXPW1RSir4aQYEr7a1DRrXtkMpzrIocwc
lovable_verification=EBaDc2Dz8h4RtP1C80JI
onetrust-domain-verification=b9bb73a75e76467ca3057da331c993b5
openai-domain-verification=dv-z9URGlz29DSIz7OuBytgTyFf
remote-domain-verification=6992b244-bf16-483d-8276-e5edeca4ab5d
SPF v=spf1 include:_spf.google.com include:amazonses.com include:servers.mcsv.net in...
CAALookup not available with standard resolver
Resolved in 5 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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://yieldmo.com

https://yieldmo.com

46 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://yieldmo.com20046 msHTTP/1.1nginx
A+
Crawlability
robots.txt present, sitemap with 8 URLs
PASS
robots.txt present, sitemap with 8 URLs
Info::
robots.txt is present
Got: 169 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 8 entries
Info::
Sitemap index with 8 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 169 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
# START YOAST BLOCK
# ---------------------------
User-agent: *
Disallow:

Sitemap: https://yieldmo.com/sitemap_index.xml
# ---------------------------
# END YOAST BLOCK
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

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

Preferred variant: non-www

HTTP → HTTPS

301http://yieldmo.com/ https://yieldmo.com/

Consistent

A
Domain Intelligence
yieldmo.com — via Amazon Registrar, Inc., 14 years old, hosted on Google Cloud
PASS
yieldmo.com — via Amazon Registrar, Inc., 14 years old, hosted on Google Cloud
Warning::
Domain expires in 50 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Jun 5, 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: Amazon Registrar, Inc.
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: Google Cloud
Got: AS15169
Domain expiry

EXPIRED

June 5, 2026

SSL certificate

86 days

Issued by Let's Encrypt

Domain age

14 years

Registered June 5, 2012

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Google Cloud

ASN AS15169

35.212.43.67

Registrar

Amazon Registrar, Inc.

Unlocked 4 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 Amazon Registrar, Inc.
Created June 5, 2012 (14 years ago)
Expires June 5, 2026 (1 months)
Last Updated May 1, 2025
Name Servers ns-1326.awsdns-37.org, ns-146.awsdns-18.com, ns-2030.awsdns-61.co.uk, ns-635.awsdns-15.net
DNSSEC Not enabled
Hosting
IP Address 35.212.43.67
ASN AS15169 (GOOGLE - Google LLC, US)
Provider Google Cloud
Data source: rdap (0.1s)

Consider enabling auto-renewal to prevent accidental expiration.

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

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.
4 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
9 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
22 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
53 ms
Total Time Total request time from DNS lookup through full response.
62 ms

Connection waterfall

DNS Lookup 4 ms TCP Connect 9 ms TLS Handshake 22 ms Server Processing 18 ms Content Transfer 9 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback