Skip to content
https://omnicreator.art

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
0
REVIEW
7
PASS
10
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
10 PASS 7 REVIEW
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/4 IPs match cert SAN
REVIEW
0/4 IPs match cert SAN
Info::
PTR lookup failed for 172.67.211.191: lookup 172.67.211.191: 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.
Info::
PTR lookup failed for 104.21.85.220: lookup 104.21.85.220: 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.
Info::
PTR lookup failed for 2606:4700:3031::ac43:d3bf: lookup 2606:4700:3031::ac43:d3bf: 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.
Info::
PTR lookup failed for 2606:4700:3032::6815:55dc: lookup 2606:4700:3032::6815:55dc: 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
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 redirects to HTTPS permanently
Got: HTTP 301

www / non-www

200https://www.omnicreator.art/
200https://omnicreator.art/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://omnicreator.art/ → https://omnicreator.art/

Consistent

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

Certificate validity

82
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
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
2 A records, 36 ms lookup
PASS
2 A records, 36 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 172.67.211.191, 104.21.85.220
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:3031::ac43:d3bf, 2606:4700:3032::6815:55dc
Info::
2 nameserver(s) configured
Got: liberty.ns.cloudflare.com, lee.ns.cloudflare.com
Info::
5 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 36 ms
Got: 36 ms
A172.67.211.191, 104.21.85.220
AAAA2606:4700:3031::ac43:d3bf, 2606:4700:3032::6815:55dc
CNAME—
NSliberty.ns.cloudflare.com, lee.ns.cloudflare.com
MX
10 eforward2.registrar-servers.com
10 eforward1.registrar-servers.com
10 eforward3.registrar-servers.com
15 eforward4.registrar-servers.com
20 eforward5.registrar-servers.com
TXT
google-site-verification=WeId4Sx_6BabRzqvEDeQg43YnJkDboXMRhfx3EIcgZU
SPF v=spf1 include:spf.efwd.registrar-servers.com ~all
CAALookup not available with standard resolver
Resolved in 36 ms
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Multi-Resolver DNS Speed
Mean 31ms across 3 resolvers (spread 25ms)
PASS
Mean 31ms across 3 resolvers (spread 25ms)
Info::
Google: 20ms
Got: 20ms via 8.8.8.8:53
Info::
Quad9: 28ms
Got: 28ms via 9.9.9.9:53
Info::
Cloudflare: 45ms
Got: 45ms via 1.1.1.1:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://omnicreator.art

https://omnicreator.art

909 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://omnicreator.art200909 msHTTP/1.1cloudflare
A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2606:4700:3031::ac43:d3bf, 2606:4700:3032::6815:55dc
Got: 17 ms connect
IPv6 Ready
AAAA Records 2606:4700:3031::ac43:d3bf, 2606:4700:3032::6815:55dc Connection Reachable (17 ms)
A+
Crawlability
robots.txt present, sitemap with 124 URLs
PASS
robots.txt present, sitemap with 124 URLs
Info::
robots.txt is present
Got: 191 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 124 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 191 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-Agent: *
Allow: /
Disallow: /api/
Disallow: /settings/
Disallow: /dashboard/
Disallow: /auth/

Sitemap: https://omnicreator.art/sitemap.xml
# LLM brief: https://omnicreator.art/llms.txt

A+
Domain Intelligence
omnicreator.art — via NameCheap, Inc., 3 months old
PASS
omnicreator.art — via NameCheap, Inc., 3 months old
Info::
Domain registered until Jul 14, 2027 (9 months remaining)
Info::
Domain is only 3 months old
Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.
Got: Registered Jul 14, 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: NameCheap, 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.
Domain expiry

269 days

July 14, 2027

SSL certificate

82 days

Issued by Google Trust Services

Domain age

3 months

Registered July 14, 2026

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:3031::ac43:d3bf

Registrar

NameCheap, 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
  • Newly registered domain — build backlinks and content to establish SEO trust
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar NameCheap, Inc.
Created July 14, 2026 (3 months ago)
Expires July 14, 2027 (9 months)
Last Updated August 1, 2026
Name Servers lee.ns.cloudflare.com, liberty.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700:3031::ac43:d3bf
Data source: rdap (0.3s)

Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.

Why this matters

Informational: domain age. Newer domains may have lower trust signals in spam/security filters.

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

Connection waterfall

DNS Lookup 37 ms TCP Connect 17 ms TLS Handshake 28 ms Server Processing 563 ms Content Transfer 4 ms
A+
CDN & Delivery
Cloudflare (HIT)
PASS
Cloudflare (HIT)
Info::
Document is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: a4c19fa28d34bb66-CDG
Info::
CDN cache status: HIT
Document served via CDN: Cloudflare
Provider Cloudflare Cache Status HIT Evidence cf-ray: a4c19fa28d34bb66-CDG
A+
CDN Cache Observability
Cache state: HIT
PASS
Cache state: HIT
Info::
CDN cache state observable via 2 header(s)
Got: age=1467, cf-cache-status=HIT
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback