Skip to content
https://hakobujp.pro

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
89
GRADE
B
FIX
0
REVIEW
7
PASS
10
INFO
0
Probed from New York, United Stated
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 104.21.26.145: lookup 104.21.26.145: 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 172.67.136.130: lookup 172.67.136.130: 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:3034::ac43:8882: lookup 2606:4700:3034::ac43:8882: 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:3036::6815:1a91: lookup 2606:4700:3036::6815:1a91: 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.hakobujp.pro/
200https://hakobujp.pro/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://hakobujp.pro/ → https://hakobujp.pro/

Consistent

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

Connection waterfall

DNS Lookup 88 ms TCP Connect 2 ms TLS Handshake 10 ms Server Processing 722 ms Content Transfer 2 ms
B
TLS Certificate Expiry & Recommendations
78 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • 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.
A+
DNS Records
2 A records, 37 ms lookup
PASS
2 A records, 37 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.21.26.145, 172.67.136.130
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:3034::ac43:8882, 2606:4700:3036::6815:1a91
Info::
2 nameserver(s) configured
Got: brit.ns.cloudflare.com, ganz.ns.cloudflare.com
Info::
No MX records — email not configured via DNS
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 37 ms
Got: 37 ms
A104.21.26.145, 172.67.136.130
AAAA2606:4700:3034::ac43:8882, 2606:4700:3036::6815:1a91
CNAME—
NSbrit.ns.cloudflare.com, ganz.ns.cloudflare.com
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 37 ms

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

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 32ms across 3 resolvers (spread 71ms)
PASS
Mean 32ms across 3 resolvers (spread 71ms)
Info::
Cloudflare: 6ms
Got: 6ms via 1.1.1.1:53
Info::
Quad9: 15ms
Got: 15ms via 9.9.9.9:53
Info::
Google: 77ms
Got: 77ms via 8.8.8.8:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://hakobujp.pro

https://hakobujp.pro

860 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://hakobujp.pro200860 msHTTP/1.1cloudflare
A+
IPv6 Readiness
IPv6 reachable (2 ms)
PASS
IPv6 reachable (2 ms)
Info::
IPv6 is configured and reachable at 2606:4700:3034::ac43:8882, 2606:4700:3036::6815:1a91
Got: 2 ms connect
IPv6 Ready
AAAA Records 2606:4700:3034::ac43:8882, 2606:4700:3036::6815:1a91 Connection Reachable (2 ms)
A+
Crawlability
robots.txt present, sitemap with 3 URLs
PASS
robots.txt present, sitemap with 3 URLs
Info::
robots.txt is present
Got: 170 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 3 entries
Info::
Sitemap index with 3 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 170 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
# START YOAST BLOCK
# ---------------------------
User-agent: *
Disallow:

Sitemap: https://hakobujp.pro/sitemap_index.xml
# ---------------------------
# END YOAST BLOCK
sitemap.xml 200 OK
Type Sitemap Index URLs 3 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
hakobujp.pro — via Dynadot Inc, 4 months old
PASS
hakobujp.pro — via Dynadot Inc, 4 months old
Info::
Domain registered until Jun 12, 2027 (7 months remaining)
Info::
Domain is only 4 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 Jun 12, 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: Dynadot 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

234 days

June 12, 2027

SSL certificate

78 days

Issued by Google Trust Services

Domain age

4 months

Registered June 12, 2026

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:3034::ac43:8882

Registrar

Dynadot 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 Dynadot Inc
Created June 12, 2026 (4 months ago)
Expires June 12, 2027 (7 months)
Last Updated August 13, 2026
Name Servers brit.ns.cloudflare.com, ganz.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700:3034::ac43:8882
Data source: rdap (0.2s)

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
CDN & Delivery
Cloudflare (DYNAMIC)
PASS
Cloudflare (DYNAMIC)
Info::
Document is served via Cloudflare CDN (edge: EWR)
Got: cf-ray: a4d960d498457aa6-EWR
Info::
CDN cache status: DYNAMIC
Document served via CDN: Cloudflare
Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: a4d960d498457aa6-EWR
A+
CDN Cache Observability
Cache state: DYNAMIC
PASS
Cache state: DYNAMIC
Info::
CDN cache state observable via 1 header(s)
Got: cf-cache-status=DYNAMIC
A+
Health Check Endpoint
Health endpoint at https://hakobujp.pro/api/health (HTTP 200)
PASS
Health endpoint at https://hakobujp.pro/api/health (HTTP 200)
Info::
Public health endpoint at https://hakobujp.pro/api/health
Got: https://hakobujp.pro/api/health
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback