Skip to content
https://netvideogirls.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
86
GRADE
B
FIX
1
REVIEW
9
PASS
7
INFO
0
Probed from Sao Paulo, Brazil
200 OK
Checks
17
7 PASS 9 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.

B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
B
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
No CAA records published
Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.
C
Reverse DNS
Action
0/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR lookup failed for 99.192.157.102: lookup 99.192.157.102: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
B
Multi-Resolver DNS Speed
Mean 45ms across 3 resolvers (spread 120ms)
REVIEW
Mean 45ms across 3 resolvers (spread 120ms)
Info::
Cloudflare: 5ms
Got: 5ms via 1.1.1.1:53
Info::
Quad9: 6ms
Got: 6ms via 9.9.9.9:53
Info::
Google: 125ms
Got: 125ms via 8.8.8.8:53
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
74 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

74
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
B
CDN Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
No CDN cache-status headers in the response
Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.
A+
DNS Records
1 A records, 9 ms lookup
PASS
1 A records, 9 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 99.192.157.102
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: algin.ns.cloudflare.com, kiki.ns.cloudflare.com
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 9 ms
Got: 9 ms
A99.192.157.102
AAAA
CNAME
NSalgin.ns.cloudflare.com, kiki.ns.cloudflare.com
MX
10 mail.netvideogirls.com
TXT
google-site-verification=X_iPAPbIsSV_Xc5iGdTI7ocT4T4dI3mzK8bYlSUQ5yw
SPF v=spf1 a mx a:mail.netvideogirls.com ip4:99.192.157.96/27 include:amazonses.com ...
CAALookup not available with standard resolver
Resolved in 9 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

A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://netvideogirls.com

https://netvideogirls.com

446 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://netvideogirls.com200446 msHTTP/1.1Apache
A+
Crawlability
robots.txt present, sitemap with 76 URLs
PASS
robots.txt present, sitemap with 76 URLs
Info::
robots.txt is present
Got: 241 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 76 entries
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 241 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /2257
Disallow: /support
Disallow: /terms-and-conditions
Disallow: /privacy-policy
Disallow: /content-removal
Disallow: /sblogin/
Disallow: /cgi-bin/
Disallow: /static/65030c691088e98506465aa4a485affe/8f027/2257.webp

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.netvideogirls.com/
200https://netvideogirls.com/

Preferred variant: non-www

HTTP → HTTPS

301http://netvideogirls.com/ https://netvideogirls.com/

Consistent

A+
Domain Intelligence
netvideogirls.com — via Name.com, Inc., 26 years, 6 months old, hosted on MOJOHOST - MOJOHOST, US
PASS
netvideogirls.com — via Name.com, Inc., 26 years, 6 months old, hosted on MOJOHOST - MOJOHOST, US
Info::
Domain registered until May 18, 2032 (5 years, 11 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: Name.com, 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: MOJOHOST - MOJOHOST, US
Got: AS27589
Domain expiry

2137 days

May 18, 2032

SSL certificate

74 days

Issued by Sectigo Limited

Domain age

26 years, 6 months

Registered May 18, 2000

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

MOJOHOST - MOJOHOST, US

ASN AS27589

99.192.157.102

Registrar

Name.com, Inc.

Unlocked 2 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 Name.com, Inc.
Created May 18, 2000 (26 years, 6 months ago)
Expires May 18, 2032 (5 years, 11 months)
Last Updated March 13, 2025
Name Servers algin.ns.cloudflare.com, kiki.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 99.192.157.102
ASN AS27589 (MOJOHOST - MOJOHOST, US)
Provider MOJOHOST - MOJOHOST, US
Data source: rdap (0.7s)

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

Connection waterfall

DNS Lookup 12 ms TCP Connect 109 ms TLS Handshake 223 ms Server Processing 112 ms Content Transfer 110 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback