Skip to main content

Engineer's DNS Intelligence Report

haukeflix.top
8 Mar 2026, 01:30 UTC · 3.0s ·v26.35.17 · SHA-3-512: d7d5✱✱✱✱ Verify
Recon ModeRecon Mode Snapshot Re-analyze New Domain
Footprint
DNS Security & Trust Posture
Risk Level: Low Risk
4 protocols configured, 5 not configured Why we go beyond letter grades
Analysis Confidence (ICD 203)
MODERATE 71/100
Resolver agreement is inconsistent for some protocols, limiting confidence. Data currency and system maturity are adequate.
Accuracy 63% Currency 80/100 Maturity verified
Limiting factor: Resolver agreement is low for this scan — some protocols returned inconsistent results across resolvers
Intelligence Currency
Data Currency: Good 80/100
ICuAE Details
Currentness Excellent TTL Compliance Excellent Completeness Degraded Source Credibility Excellent TTL Relevance Adequate
DNS data is mostly current with minor gaps — good intelligence currency

The following DNS record TTLs deviate from recommended values. Incorrect TTLs can cause caching issues, slow propagation, or unnecessary DNS traffic.

Record Type Observed TTL Typical TTL Severity Context
A 569s 1 hour (3600s) medium A TTL is below typical — observed 569s, typical value is 1 hour (3600s). Short TTLs increase DNS query volume but enable faster propagation. If you are preparing for a migration or need rapid failover, this may be intentional (RFC 1035 §3.2.1). For steady-state production, consider 3600 seconds per NIST SP 800-53 SI-18 relevance guidance. Use the TTL Tuner for profile-specific recommendations.
NS 21539s 1 day (86400s) medium NS TTL is below typical — observed 21539s, typical value is 1 day (86400s). Short TTLs increase DNS query volume but enable faster propagation. If you are preparing for a migration or need rapid failover, this may be intentional (RFC 1035 §3.2.1). For steady-state production, consider 86400 seconds per NIST SP 800-53 SI-18 relevance guidance. Use the TTL Tuner for profile-specific recommendations.
AAAA 10 minutes (600s) 1 hour (3600s) medium AAAA TTL is below typical — observed 10 minutes (600s), typical value is 1 hour (3600s). Short TTLs increase DNS query volume but enable faster propagation. If you are preparing for a migration or need rapid failover, this may be intentional (RFC 1035 §3.2.1). For steady-state production, consider 3600 seconds per NIST SP 800-53 SI-18 relevance guidance. Use the TTL Tuner for profile-specific recommendations.
TXT 10 minutes (600s) 1 hour (3600s) medium TXT TTL is below typical — observed 10 minutes (600s), typical value is 1 hour (3600s). Short TTLs increase DNS query volume but enable faster propagation. If you are preparing for a migration or need rapid failover, this may be intentional (RFC 1035 §3.2.1). For steady-state production, consider 3600 seconds per NIST SP 800-53 SI-18 relevance guidance. Use the TTL Tuner for profile-specific recommendations.
MX 10 minutes (600s) 1 hour (3600s) medium MX TTL is below typical — observed 10 minutes (600s), typical value is 1 hour (3600s). Short TTLs increase DNS query volume but enable faster propagation. If you are preparing for a migration or need rapid failover, this may be intentional (RFC 1035 §3.2.1). For steady-state production, consider 3600 seconds per NIST SP 800-53 SI-18 relevance guidance. Use the TTL Tuner for profile-specific recommendations.

Big Picture Questions

  • How often do you actually change this record? If it hasn’t changed in months, a short TTL is generating unnecessary DNS queries without any benefit.
  • Are you preparing for a migration or IP change? Short TTLs make sense temporarily — but should be raised back to 1 hour (3600s) once the change is complete.
  • Every DNS lookup adds 20–150ms of latency. With a 60s TTL, returning visitors trigger a fresh lookup every minute. With 3600s, they get cached responses for an hour — faster page loads, no extra infrastructure needed.
  • Google runs A records at ~30s because they operate a global anycast network and need to steer traffic dynamically. For a typical website without that infrastructure, copying those TTLs increases query volume with zero upside.
Tune TTL for haukeflix.top
Reference: NIST SP 800-53 SI-7 (Information Integrity) · RFC 8767 (Serve Stale) · RFC 1035 §3.2.1 (TTL semantics) DNS provider detected: Porkbun — provider-specific RFC compliance notes are shown inline above where applicable.
Primary NS curitiba.ns.porkbun.com
Serial 2398107372
Admin dns.cloudflare.com
Provider Porkbun
Timer Value RFC 1912 Range
Refresh10000s1,200–43,200s (20 min – 12 hrs)
Retry2400sFraction of Refresh
Expire604800s1,209,600–2,419,200s (14–28 days)
Minimum (Neg. Cache)1800s300–86,400s (5 min – 1 day)
Expire: SOA Expire is 7 days (604800s). RFC 1912 §2.2 recommends 1,209,600–2,419,200 seconds (14–28 days). If the primary nameserver becomes unreachable, secondary nameservers will stop serving this zone after only 7 days (604800s).
Email Spoofing
Protected
Brand Impersonation
Not Setup
DNS Tampering
Protected
Certificate Control
Open
Recommended
Add DMARC aggregate reporting (rua) for visibility into email authentication
Configured
SPF (hard fail), DMARC (reject), DKIM (not applicable — no-mail domain), DNSSEC
Not Configured
MTA-STS, TLS-RPT, BIMI, DANE, CAA
Priority Action Achievable posture: Secure
Low Add CAA Records

CAA records specify which Certificate Authorities may issue certificates for your domain, reducing the risk of unauthorized certificate issuance.

CAA constrains which CAs can issue certificates for this domain.
FieldValue
TypeCAA
Hosthaukeflix.top (root of domain — adjust CA to match your provider)
Value0 issue "letsencrypt.org"
Registrar (RDAP) OBSERVED LIVE
Porkbun LLC
Where domain was purchased
Email Service Provider
No Mail Domain
No-Mail Domain — Fully Hardened
Web Hosting
Unknown
Where website is hosted
DNS Hosting
Unknown
Where DNS records are edited
Email Security Methodology Can this domain be impersonated by email? No null MX indicates no-mail domain
No-Mail Domain — Fully Hardened 3/3 controls
This domain declares it does not send or receive email and has all three RFC-recommended controls in place: Null MX (RFC 7505), SPF -all (RFC 7208), and DMARC reject (RFC 7489).
DMARC reject (RFC 7489) Null MX (RFC 7505) SPF -all (RFC 7208)

SPF Record RFC 7208 §4 Verified

Does this domain declare who may send email on its behalf? Yes
Success -all

Valid SPF (no mail allowed) - domain declares it sends no email

v=spf1 -all
RFC 7208 Conformant — This SPF record conforms to the syntax and semantics defined in RFC 7208 §4.
RFC Failure Mode: Unlike DMARC (where unknown tags are silently ignored per RFC 7489 §6.3), SPF with unrecognized mechanisms produces a PermError per RFC 7208 §4.6 — the record fails loudly rather than silently.
Related CVEs: CVE-2024-7208 (multi-tenant domain spoofing), CVE-2024-7209 (shared SPF exploitation), CVE-2023-51764 (SMTP smuggling bypasses SPF)

DMARC Policy RFC 7489 §6.3 Verified

Are spoofed emails rejected or quarantined? Yes — reject policy
Success p=reject

DMARC policy reject (100%) - excellent protection

v=DMARC1; p=reject;
Alignment: SPF relaxed DKIM relaxed
No np= tag (DMARCbis) — non-existent subdomains inherit p= policy but adding np=reject provides explicit protection against subdomain spoofing
No aggregate reporting (rua) configured — you won't receive reports about authentication results and potential abuse
No forensic reporting (ruf) tag — this is correct. The absence of ruf= is not a gap. RFC 7489 §7.3 warns that forensic reports can expose PII (full message headers or bodies). Google, Microsoft, and Yahoo do not honour ruf= requests regardless. The DMARCbis draft (draft-ietf-dmarc-dmarcbis) has formally removed ruf= from the specification, confirming its deprecation. Omitting ruf= is the recommended modern practice. RFC 7489 §7.3 — Forensic Reports
RFC 7489 Conformant — DMARC record conforms to RFC 7489 §6.3 with full enforcement.
DMARCbis (Pending): draft-ietf-dmarc-dmarcbis will elevate DMARC to Standards Track, obsolete RFC 7489, replace pct= with t= (testing flag), add np= (non-existent subdomain policy), and mandate DNS tree walk for policy discovery instead of the Public Suffix List.
Related CVEs: CVE-2024-49040 (Exchange sender spoofing), CVE-2024-7208 (multi-tenant DMARC bypass)

DKIM Records RFC 6376 §3.6 Verified

Are outbound emails cryptographically signed? Not discoverable
Weak Keys

Found 81 DKIM selector(s) but some keys are revoked

Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
Key revoked (p= empty)
amazonses._domainkey Amazon SES
v=DKIM1; p=
barracuda._domainkey Barracuda
v=DKIM1; p=
brevo._domainkey Brevo (Sendinblue)
v=DKIM1; p=
cisco._domainkey
v=DKIM1; p=
cm._domainkey Campaign Monitor
v=DKIM1; p=
ctct1._domainkey Constant Contact
v=DKIM1; p=
ctct2._domainkey Constant Contact
v=DKIM1; p=
customerio._domainkey Customer.io
v=DKIM1; p=
default._domainkey
v=DKIM1; p=
dk._domainkey ActiveCampaign
v=DKIM1; p=
dkim._domainkey
v=DKIM1; p=
dkim1._domainkey
v=DKIM1; p=
dkim2._domainkey
v=DKIM1; p=
dkim3._domainkey
v=DKIM1; p=
drip._domainkey Drip
v=DKIM1; p=
em._domainkey SendGrid
v=DKIM1; p=
email._domainkey
v=DKIM1; p=
everlytickey1._domainkey Everlytic
v=DKIM1; p=
everlytickey2._domainkey Everlytic
v=DKIM1; p=
fm1._domainkey
v=DKIM1; p=
fm2._domainkey
v=DKIM1; p=
fm3._domainkey
v=DKIM1; p=
freshdesk._domainkey Freshdesk
v=DKIM1; p=
google._domainkey Google Workspace
v=DKIM1; p=
google2048._domainkey Google Workspace
v=DKIM1; p=
hornet._domainkey Hornetsecurity
v=DKIM1; p=
hs1._domainkey HubSpot
v=DKIM1; p=
hs2._domainkey HubSpot
v=DKIM1; p=
hubspot._domainkey HubSpot
v=DKIM1; p=
intercom._domainkey Intercom
v=DKIM1; p=
k1._domainkey
v=DKIM1; p=
k2._domainkey
v=DKIM1; p=
k3._domainkey MailChimp
v=DKIM1; p=
key1._domainkey
v=DKIM1; p=
key2._domainkey
v=DKIM1; p=
klaviyo._domainkey Klaviyo
v=DKIM1; p=
mail._domainkey
v=DKIM1; p=
mailchimp._domainkey MailChimp
v=DKIM1; p=
mailer._domainkey
v=DKIM1; p=
mailgun._domainkey Mailgun
v=DKIM1; p=
mailjet._domainkey Mailjet
v=DKIM1; p=
mandrill._domainkey MailChimp (Mandrill)
v=DKIM1; p=
mandrill2._domainkey MailChimp (Mandrill)
v=DKIM1; p=
mc._domainkey MailChimp
v=DKIM1; p=
mimecast._domainkey Mimecast
v=DKIM1; p=
ml._domainkey MailerLite
v=DKIM1; p=
mta._domainkey
v=DKIM1; p=
mta1._domainkey
v=DKIM1; p=
mta2._domainkey
v=DKIM1; p=
mx._domainkey
v=DKIM1; p=
postmark._domainkey Postmark
v=DKIM1; p=
proofpoint._domainkey Proofpoint
v=DKIM1; p=
protonmail._domainkey
v=DKIM1; p=
protonmail2._domainkey
v=DKIM1; p=
protonmail3._domainkey
v=DKIM1; p=
s1._domainkey
v=DKIM1; p=
s2._domainkey
v=DKIM1; p=
s3._domainkey
v=DKIM1; p=
salesforce._domainkey Salesforce
v=DKIM1; p=
selector1._domainkey
v=DKIM1; p=
selector2._domainkey
v=DKIM1; p=
selector3._domainkey
v=DKIM1; p=
sendgrid._domainkey SendGrid
v=DKIM1; p=
sendgrid2._domainkey SendGrid
v=DKIM1; p=
sendinblue._domainkey Brevo (Sendinblue)
v=DKIM1; p=
sf1._domainkey Salesforce
v=DKIM1; p=
sf2._domainkey Salesforce
v=DKIM1; p=
sig1._domainkey
v=DKIM1; p=
sig2._domainkey
v=DKIM1; p=
smtp._domainkey
v=DKIM1; p=
smtpapi._domainkey SendGrid
v=DKIM1; p=
sparkpost._domainkey SparkPost
v=DKIM1; p=
sq._domainkey Square Online
v=DKIM1; p=
square._domainkey Square Online
v=DKIM1; p=
squareup._domainkey Square Online
v=DKIM1; p=
turbo-smtp._domainkey
v=DKIM1; p=
zendesk1._domainkey Zendesk
v=DKIM1; p=
zendesk2._domainkey Zendesk
v=DKIM1; p=
zmail._domainkey Zoho Mail
v=DKIM1; p=
zoho._domainkey Zoho Mail
v=DKIM1; p=
zohomail._domainkey Zoho Mail
v=DKIM1; p=
RFC Stance: RFC 6376 (Internet Standard) defines the DKIM mechanism. DKIM selectors are not publicly enumerable — absence in a scan does not prove absence of signing.
Known Vulnerabilities: DKIM l= tag body length vulnerability (attacker appends unsigned content to signed mail), weak key exploitation (keys below 1024-bit are cryptographically breakable per RFC 6376 §3.3.3), DKIM replay attacks (re-sending legitimately signed messages at scale)

MTA-STS RFC 8461 §3 Verified

Can attackers downgrade SMTP to intercept mail? Not prevented
Warning

No valid MTA-STS record found

MTA-STS policy enforcement is evaluated in Mail Transport Security below.

TLS-RPT RFC 8460 §3 Verified

Will failures in TLS delivery be reported? No reporting
Warning

No valid TLS-RPT record found


DANE / TLSA Verified Recon Methodology Can mail servers establish identity without a public CA? No
RFC 7672 §3 RFC 6698 §2 Not Configured

No valid MX hosts — DANE check skipped

DANE (RFC 7672) binds TLS certificates to DNSSEC-signed DNS records, protecting email transport against man-in-the-middle attacks and rogue CAs. It is the primary transport security standard — MTA-STS (RFC 8461) was created as the alternative for domains that cannot deploy DNSSEC. Over 1 million domains use DANE globally, including Microsoft Exchange Online, Proton Mail, and Fastmail. Best practice: deploy both for defense in depth.

Email Transport Security

Two mechanisms protect email in transit. DANE is the primary standard; MTA-STS is the alternative for domains that cannot deploy DNSSEC:

  • DNSSEC + DANE (RFC 7672) — Cryptographic chain of trust from DNS root to mail server certificate. Eliminates reliance on certificate authorities. No trust-on-first-use weakness. Requires DNSSEC.
  • MTA-STS (RFC 8461) — HTTPS-based policy requiring TLS for mail delivery. Works without DNSSEC but relies on CA trust and is vulnerable on first use (§10). Created for domains where “deploying DNSSEC is undesirable or impractical” (§2).
This domain has neither DANE nor MTA-STS. Mail transport relies on opportunistic TLS without policy enforcement, leaving it vulnerable to downgrade attacks. Deploy DANE (RFC 7672) with DNSSEC for the strongest protection, or MTA-STS (RFC 8461) if DNSSEC is not feasible.

Industry trend: Microsoft Exchange Online enforces inbound DANE with DNSSEC (GA October 2024), and providers like Proton Mail and Fastmail also support DANE. Google Workspace does not support DANE and relies on MTA-STS. Both mechanisms coexist because DANE is backward-compatible — senders skip the check if the domain isn't DNSSEC-signed (RFC 7672 §1.3).


Brand Security Can this brand be convincingly faked? Possible DMARC reject policy blocks email spoofing (RFC 7489 §6.3), but no BIMI brand verification and no CAA certificate restriction (RFC 8659) — visual impersonation via lookalike domains and unrestricted certificate issuance remain open vectors

BIMI BIMI Spec Verified Warning

Is the brand identity verified and displayed in inboxes? No

No valid BIMI record found

CAA RFC 8659 §4 Verified Warning

Does this domain restrict who can issue TLS certificates? No

No CAA records found - any CA can issue certificates

Vulnerability Disclosure Policy (security.txt) Is there a verified way to report security issues? No RFC 9116

No security.txt found

A security.txt file at /.well-known/security.txt provides security researchers with a standardized way to report vulnerabilities. See securitytxt.org for a generator.

AI Surface Scanner Beta Is this domain discoverable by AI — and protected from abuse? No

No AI governance measures detected

llms.txt llmstxt.org
Is this domain publishing AI-readable brand context? No
No llms.txt found
No llms-full.txt found
AI Crawler Governance (robots.txt) RFC 9309 IETF Draft
Are AI crawlers explicitly allowed or blocked? Not blocked
No AI crawler blocking observed — no blocking directives found in robots.txt
Content-Usage Directive IETF Draft
Does the site express AI content-usage preferences? Not Configured
No Content-Usage directive detected. The IETF AI Preferences working group is developing a Content-Usage: directive for robots.txt that lets site owners declare whether their content may be used for AI training and inference. This is an active draft, not yet a ratified standard.
Example: Add Content-Usage: ai=no to robots.txt to deny AI training, or Content-Usage: ai=allow to explicitly permit it. Without this directive, AI crawler behavior depends on individual crawler policies and User-agent rules.
AI Recommendation Poisoning
Is this site trying to manipulate AI recommendations? No
No AI recommendation poisoning indicators found
Hidden Prompt Artifacts
Is hidden prompt-injection text present in the source? No
No hidden prompt-like artifacts detected
Evidence Log (1 item)
TypeDetailSeverityConfidence
robots_txt_no_ai_blocks robots.txt found but no AI-specific blocking directives low Observed
Public Exposure Checks Are sensitive files or secrets exposed? No

No exposed secrets detected in public page source — same-origin, non-intrusive scan of publicly visible page source and scripts.

No exposed secrets, API keys, or credentials were detected in publicly accessible page source or scripts.
Sources scanned (1)
  • https://haukeflix.top/
What type of scan is this?

This is OSINT (Open Source Intelligence) collection — we check the same publicly accessible URLs that any web browser could visit. No authentication is bypassed, no ports are probed, no vulnerabilities are exploited.

Is this a PCI compliance scan? No. PCI DSS requires scans performed by an Approved Scanning Vendor (ASV) certified by the PCI Security Standards Council. DNS Tool is not an ASV. If you need PCI compliance scanning, engage a certified ASV such as Qualys, Tenable, or Trustwave.

Is this a penetration test? No. Penetration testing involves active exploitation attempts against systems with authorization. Our checks are passive observation of publicly accessible resources — the same methodology used by Shodan, Mozilla Observatory, and other OSINT platforms.

DNS Server Security Hardened

No DNS server misconfigurations found on maceio.ns.porkbun.com — Nmap NSE probes for zone transfer (AXFR), open recursion (RFC 5358), nameserver identity disclosure, and DNS cache snooping.

Check Result Detail
Zone Transfer (AXFR) Denied Zone transfer denied (correct configuration)
Open Recursion Disabled Recursion disabled (correct configuration)
Nameserver Identity Hidden No nameserver identity information disclosed
Cache Snooping Protected Cache snooping not possible (correct configuration)

Tested nameservers: maceio.ns.porkbun.com, fortaleza.ns.porkbun.com, curitiba.ns.porkbun.com, salvador.ns.porkbun.com

Delegation Consistency 1 Issue

Delegation consistency: 1 issue(s) found — Parent/child NS delegation alignment: DS↔DNSKEY, glue records, TTL drift, SOA serial sync.

Findings:
  • Could not retrieve NS TTL from parent zone

DS ↔ DNSKEY Alignment Aligned

DS Key TagDS AlgorithmDNSKEY Key TagDNSKEY Algorithm
2371 13 2371 13

Glue Record Completeness Complete

NameserverIn-BailiwickIPv4 GlueIPv6 GlueStatus
curitiba.ns.porkbun.com No N/A N/A OK
fortaleza.ns.porkbun.com No N/A N/A OK
maceio.ns.porkbun.com No N/A N/A OK
salvador.ns.porkbun.com No N/A N/A OK

NS TTL Comparison Drift

Child TTL: 86400s Drift: 0s

SOA Serial Consistency Consistent

curitiba.ns.porkbun.com: 2.398107372e+09
fortaleza.ns.porkbun.com: 2.398107372e+09
maceio.ns.porkbun.com: 2.398107372e+09
salvador.ns.porkbun.com: 2.398107372e+09
Nameserver Fleet Matrix Healthy

Analyzed 4 nameserver(s) for haukeflix.top — Per-nameserver reachability, ASN diversity, SOA serial sync, and lame delegation checks.

Nameserver IPv4 IPv6 ASN / Operator UDP TCP AA SOA Serial
salvador.ns.porkbun.com 162.159.10.150 2400:cb00:2049:1::a29f:a96 AS13335
Cloudflare, Inc.
2398107372
curitiba.ns.porkbun.com 173.245.58.37 2400:cb00:2049:1::adf5:3a25 AS13335
Cloudflare, Inc.
2398107372
fortaleza.ns.porkbun.com 162.159.8.140 2400:cb00:2049:1::a29f:88c AS13335
Cloudflare, Inc.
2398107372
maceio.ns.porkbun.com 162.159.11.180 2400:cb00:2049:1::a29f:bb4 AS13335
Cloudflare, Inc.
2398107372
Unique ASNs
1
Unique Operators
1
Unique /24 Prefixes
4
Diversity Score
Fair

1 ASN(s), 4 /24 prefix(es) — consider adding diversity

DNSSEC Operations Deep Dive 1 Issue

DNSSEC operational notes: 1 item(s) to review — KSK/ZSK differentiation, RRSIG expiry windows, NSEC/NSEC3 analysis, and rollover readiness.

Findings:
  • CDS/CDNSKEY automation present but only single KSK — pre-publish second KSK before rollover

DNSKEY Inventory 2 Keys

RoleKey TagAlgorithmKey Size
ZSK 34505 ECDSA P-256/SHA-256 256 bits
KSK 2371 ECDSA P-256/SHA-256 256 bits

RRSIG Signatures 0 Signatures

No RRSIG records found.

Denial of Existence NSEC

NSEC records expose zone contents via ordered names (zone walking). Consider NSEC3 for zone enumeration protection.

Rollover Readiness Partial

Multiple KSKs:
CDS Published:
CDNSKEY Published:
Automation: full
Mail Transport Security Beta Is mail transport encrypted and verified? No No MTA-STS or DANE — mail transport encryption is opportunistic only

No MX records found

Policy Assessment Primary

No transport enforcement policies detected. Mail delivery relies on opportunistic STARTTLS, which is vulnerable to downgrade attacks (RFC 3207). Consider deploying MTA-STS (RFC 8461) or DANE (RFC 7672).

Telemetry
TLS-RPT not configured — domain has no visibility into TLS delivery failures from real senders
Live Probe Supplementary
Skipped — No MX records found for this domain
Infrastructure Intelligence Who hosts this domain and what services power it? Direct

ASN / Network Success

Resolved 1 unique ASN(s) across 2 IP address(es)

ASNNameCountry
AS24940 Hetzner Online GmbH DE
IPv4 Mappings:
95.216.5.59AS24940 (95.216.0.0/16)
IPv6 Mappings:
2a01:4f9:2a:550::2AS24940 (2a01:4f9::/32)

Edge / CDN Success

Domain appears to use direct origin hosting

SaaS TXT Footprint Success

No SaaS services detected

Detects SaaS services that leave DNS TXT verification records (e.g., domain ownership proofs). Does not detect all SaaS platforms — only those indicated by DNS.


Domain Security Methodology Can DNS responses be tampered with in transit? No DNSSEC signed and validated, cryptographic chain of trust verified

DNSSEC RFC 4033 §2 Verified Signed ECDSA P-256/SHA-256 Modern

DNSSEC fully configured and validated — AD (Authenticated Data) flag set by resolver 8.8.8.8 confirming cryptographic chain of trust from root to zone (RFC 4035 §3.2.3)

Algorithm Observation: ECDSA P-256/SHA-256 — MUST implement, recommended default (RFC 8624 §3.1)
All current DNSSEC algorithms use classical cryptography. Post-quantum DNSSEC standards are in active IETF development (draft-sheth-pqc-dnssec-strategy) but no PQC algorithms have been standardized for DNSSEC yet.
Chain of trust: Root → TLD → Domain. DNS responses are authenticated and tamper-proof.
AD Flag: Validated - Resolver (8.8.8.8) confirmed cryptographic signatures
DS Record (at registrar):
2371 13 2 89D65B6D8E7E4E60AE9C9CF8074199D1A99B2744F191EC4E153B0680BB20BEDF

NS Delegation Verified

4 nameserver(s) configured

Nameservers: curitiba.ns.porkbun.com fortaleza.ns.porkbun.com maceio.ns.porkbun.com salvador.ns.porkbun.com
Multi-Resolver Verification Recon: Consensus reached - 5 resolvers (Cloudflare, Google, Quad9, OpenDNS, DNS4EU) agree on DNS records

CDS / CDNSKEY (DNSSEC Automation) RFC 7344 Success CDS CDNSKEY

Full RFC 8078 automated DNSSEC key rollover signaling detected (CDS + CDNSKEY)

Key TagAlgorithmDigest TypeDigest
2371 ECDSAP256SHA256 2
CDNSKEY Records:
FlagsProtocolAlgorithmPublic Key
257 3 ECDSAP256SHA256
Traffic & Routing Where does this domain's traffic actually terminate?

AIPv4 Address

95.216.5.59
Where the domain points for web traffic

AAAAIPv6 Address

2a01:4f9:2a:550::2
IPv6 ready

MXMail Servers

0 .
Null MX RFC 7505
Domain explicitly does not accept email

SRVServices

No SRV records
No service-specific routing configured
Web: Reachable (1 IPv4, 1 IPv6) Mail: Null MX (no mail) Services: None
Subdomain Discovery RFC 6962 Recon LIVE What subdomains and infrastructure are exposed in certificate logs? 486 subdomains discovered
How did we find these?
CT logs unavailable 486 current 0 expired Source: Certificate Transparency + DNS Intelligence
Subdomains discovered via CT logs (RFC 6962), DNS probing of common service names, and CNAME chain traversal.
Subdomain Source Status Provider / CNAME Certificates First Seen Issuer(s)
a.haukeflix.top DNS Current
academy.haukeflix.top DNS Current
account.haukeflix.top DNS Current
accounting.haukeflix.top DNS Current
accounts.haukeflix.top DNS Current
ad.haukeflix.top DNS Current
adfs.haukeflix.top DNS Current
admin.haukeflix.top DNS Current
admin1.haukeflix.top DNS Current
admin2.haukeflix.top DNS Current
alert.haukeflix.top DNS Current
alerts.haukeflix.top DNS Current
alpha.haukeflix.top DNS Current
analytics.haukeflix.top DNS Current
ap-south.haukeflix.top DNS Current
ap.haukeflix.top DNS Current
apac.haukeflix.top DNS Current
api.haukeflix.top DNS Current
api1.haukeflix.top DNS Current
api2.haukeflix.top DNS Current
api3.haukeflix.top DNS Current
apigw.haukeflix.top DNS Current
apis.haukeflix.top DNS Current
apm.haukeflix.top DNS Current
app.haukeflix.top DNS Current
app1.haukeflix.top DNS Current
app2.haukeflix.top DNS Current
appointments.haukeflix.top DNS Current
apps.haukeflix.top DNS Current
archive.haukeflix.top DNS Current
archives.haukeflix.top DNS Current
asia.haukeflix.top DNS Current
assets.haukeflix.top DNS Current
atom.haukeflix.top DNS Current
auth.haukeflix.top DNS Current
auth0.haukeflix.top DNS Current
autoconfig.haukeflix.top DNS Current
autodiscover.haukeflix.top DNS Current
b.haukeflix.top DNS Current
backup.haukeflix.top DNS Current
backup1.haukeflix.top DNS Current
backup2.haukeflix.top DNS Current
beta.haukeflix.top DNS Current
bi.haukeflix.top DNS Current
bigdata.haukeflix.top DNS Current
billing.haukeflix.top DNS Current
bitbucket.haukeflix.top DNS Current
blob.haukeflix.top DNS Current
blog.haukeflix.top DNS Current
booking.haukeflix.top DNS Current
broker.haukeflix.top DNS Current
bucket.haukeflix.top DNS Current
build.haukeflix.top DNS Current
builds.haukeflix.top DNS Current
c.haukeflix.top DNS Current
ca.haukeflix.top DNS Current
cache.haukeflix.top DNS Current
cal.haukeflix.top DNS Current
calendar.haukeflix.top DNS Current
campaign.haukeflix.top DNS Current
campaigns.haukeflix.top DNS Current
careers.haukeflix.top DNS Current
cart.haukeflix.top DNS Current
catalog.haukeflix.top DNS Current
cd.haukeflix.top DNS Current
cdn.haukeflix.top DNS Current
cdn1.haukeflix.top DNS Current
cdn2.haukeflix.top DNS Current
cdn3.haukeflix.top DNS Current
cert.haukeflix.top DNS Current
certs.haukeflix.top DNS Current
chat.haukeflix.top DNS Current
checkout.haukeflix.top DNS Current
ci.haukeflix.top DNS Current
client.haukeflix.top DNS Current
clients.haukeflix.top DNS Current
cloud.haukeflix.top DNS Current
cms.haukeflix.top DNS Current
cname.haukeflix.top DNS Current
code.haukeflix.top DNS Current
community.haukeflix.top DNS Current
compliance.haukeflix.top DNS Current
conference.haukeflix.top DNS Current
config.haukeflix.top DNS Current
configuration.haukeflix.top DNS Current
confluence.haukeflix.top DNS Current
connect.haukeflix.top DNS Current
console.haukeflix.top DNS Current
containers.haukeflix.top DNS Current
content.haukeflix.top DNS Current
corp.haukeflix.top DNS Current
corporate.haukeflix.top DNS Current
courses.haukeflix.top DNS Current
cpanel.haukeflix.top DNS Current
crl.haukeflix.top DNS Current
crm.haukeflix.top DNS Current
d.haukeflix.top DNS Current
dashboard.haukeflix.top DNS Current
data.haukeflix.top DNS Current
data1.haukeflix.top DNS Current
data2.haukeflix.top DNS Current
database.haukeflix.top DNS Current
datadog.haukeflix.top DNS Current
db.haukeflix.top DNS Current
db1.haukeflix.top DNS Current
db2.haukeflix.top DNS Current
dedicated.haukeflix.top DNS Current
demo.haukeflix.top DNS Current
deploy.haukeflix.top DNS Current
deployment.haukeflix.top DNS Current
dev.haukeflix.top DNS Current
dev1.haukeflix.top DNS Current
dev2.haukeflix.top DNS Current
develop.haukeflix.top DNS Current
developer.haukeflix.top DNS Current
developers.haukeflix.top DNS Current
devices.haukeflix.top DNS Current
directory.haukeflix.top DNS Current
discuss.haukeflix.top DNS Current
discussions.haukeflix.top DNS Current
dns.haukeflix.top DNS Current
dns1.haukeflix.top DNS Current
dns2.haukeflix.top DNS Current
doc.haukeflix.top DNS Current
docker.haukeflix.top DNS Current
docs.haukeflix.top DNS Current
documentation.haukeflix.top DNS Current
download.haukeflix.top DNS Current
downloads.haukeflix.top DNS Current
drupal.haukeflix.top DNS Current
e.haukeflix.top DNS Current
ecommerce.haukeflix.top DNS Current
edge.haukeflix.top DNS Current
edge1.haukeflix.top DNS Current
edge2.haukeflix.top DNS Current
education.haukeflix.top DNS Current
elastic.haukeflix.top DNS Current
elasticsearch.haukeflix.top DNS Current
email.haukeflix.top DNS Current
emea.haukeflix.top DNS Current
endpoint.haukeflix.top DNS Current
erp.haukeflix.top DNS Current
es.haukeflix.top DNS Current
etl.haukeflix.top DNS Current
eu-west.haukeflix.top DNS Current
eu.haukeflix.top DNS Current
event.haukeflix.top DNS Current
events.haukeflix.top DNS Current
exchange.haukeflix.top DNS Current
ext.haukeflix.top DNS Current
f.haukeflix.top DNS Current
faq.haukeflix.top DNS Current
feed.haukeflix.top DNS Current
feedback.haukeflix.top DNS Current
feeds.haukeflix.top DNS Current
file.haukeflix.top DNS Current
files.haukeflix.top DNS Current
finance.haukeflix.top DNS Current
firewall.haukeflix.top DNS Current
forms.haukeflix.top DNS Current
forum.haukeflix.top DNS Current
forums.haukeflix.top DNS Current
ftp.haukeflix.top DNS Current
ftp1.haukeflix.top DNS Current
ftp2.haukeflix.top DNS Current
fw.haukeflix.top DNS Current
gateway.haukeflix.top DNS Current
geo.haukeflix.top DNS Current
gis.haukeflix.top DNS Current
git.haukeflix.top DNS Current
github.haukeflix.top DNS Current
gitlab.haukeflix.top DNS Current
go.haukeflix.top DNS Current
grafana.haukeflix.top DNS Current
graphql.haukeflix.top DNS Current
gw.haukeflix.top DNS Current
gw1.haukeflix.top DNS Current
gw2.haukeflix.top DNS Current
haproxy.haukeflix.top DNS Current
health.haukeflix.top DNS Current
healthcheck.haukeflix.top DNS Current
help.haukeflix.top DNS Current
helpdesk.haukeflix.top DNS Current
hiring.haukeflix.top DNS Current
host.haukeflix.top DNS Current
hosting.haukeflix.top DNS Current
hq.haukeflix.top DNS Current
hr.haukeflix.top DNS Current
hris.haukeflix.top DNS Current
hub.haukeflix.top DNS Current
id.haukeflix.top DNS Current
identity.haukeflix.top DNS Current
image.haukeflix.top DNS Current
images.haukeflix.top DNS Current
imap.haukeflix.top DNS Current
img.haukeflix.top DNS Current
int.haukeflix.top DNS Current
internal.haukeflix.top DNS Current
intranet.haukeflix.top DNS Current
inventory.haukeflix.top DNS Current
investor.haukeflix.top DNS Current
investors.haukeflix.top DNS Current
invoice.haukeflix.top DNS Current
ir.haukeflix.top DNS Current
it.haukeflix.top DNS Current
itsm.haukeflix.top DNS Current
itsupport.haukeflix.top DNS Current
jenkins.haukeflix.top DNS Current
jira.haukeflix.top DNS Current
jobs.haukeflix.top DNS Current
k8s.haukeflix.top DNS Current
kafka.haukeflix.top DNS Current
kb.haukeflix.top DNS Current
kibana.haukeflix.top DNS Current
kong.haukeflix.top DNS Current
kubernetes.haukeflix.top DNS Current
lab.haukeflix.top DNS Current
labs.haukeflix.top DNS Current
lan.haukeflix.top DNS Current
lb.haukeflix.top DNS Current
ldap.haukeflix.top DNS Current
learn.haukeflix.top DNS Current
learning.haukeflix.top DNS Current
legal.haukeflix.top DNS Current
link.haukeflix.top DNS Current
links.haukeflix.top DNS Current
live.haukeflix.top DNS Current
lms.haukeflix.top DNS Current
loadbalancer.haukeflix.top DNS Current
location.haukeflix.top DNS Current
log.haukeflix.top DNS Current
login.haukeflix.top DNS Current
logs.haukeflix.top DNS Current
m.haukeflix.top DNS Current
mail.haukeflix.top DNS Current
mail1.haukeflix.top DNS Current
mail2.haukeflix.top DNS Current
mail3.haukeflix.top DNS Current
manage.haukeflix.top DNS Current
management.haukeflix.top DNS Current
manager.haukeflix.top DNS Current
map.haukeflix.top DNS Current
maps.haukeflix.top DNS Current
marketing.haukeflix.top DNS Current
mdm.haukeflix.top DNS Current
media.haukeflix.top DNS Current
meet.haukeflix.top DNS Current
meeting.haukeflix.top DNS Current
memcached.haukeflix.top DNS Current
metrics.haukeflix.top DNS Current
microservices.haukeflix.top DNS Current
mobile.haukeflix.top DNS Current
mongo.haukeflix.top DNS Current
mongodb.haukeflix.top DNS Current
monitor.haukeflix.top DNS Current
monitoring.haukeflix.top DNS Current
mq.haukeflix.top DNS Current
mta.haukeflix.top DNS Current
mx.haukeflix.top DNS Current
mx1.haukeflix.top DNS Current
mx2.haukeflix.top DNS Current
mx3.haukeflix.top DNS Current
mx4.haukeflix.top DNS Current
mx5.haukeflix.top DNS Current
my.haukeflix.top DNS Current
myaccount.haukeflix.top DNS Current
mysql.haukeflix.top DNS Current
na.haukeflix.top DNS Current
nagios.haukeflix.top DNS Current
net.haukeflix.top DNS Current
network.haukeflix.top DNS Current
news.haukeflix.top DNS Current
nginx.haukeflix.top DNS Current
node1.haukeflix.top DNS Current
node2.haukeflix.top DNS Current
node3.haukeflix.top DNS Current
notifications.haukeflix.top DNS Current
notify.haukeflix.top DNS Current
ns.haukeflix.top DNS Current
ns1.haukeflix.top DNS Current
ns2.haukeflix.top DNS Current
ns3.haukeflix.top DNS Current
ns4.haukeflix.top DNS Current
ns5.haukeflix.top DNS Current
ns6.haukeflix.top DNS Current
o365.haukeflix.top DNS Current
oauth.haukeflix.top DNS Current
object.haukeflix.top DNS Current
ocsp.haukeflix.top DNS Current
office.haukeflix.top DNS Current
okta.haukeflix.top DNS Current
order.haukeflix.top DNS Current
orders.haukeflix.top DNS Current
origin.haukeflix.top DNS Current
origin1.haukeflix.top DNS Current
origin2.haukeflix.top DNS Current
outlook.haukeflix.top DNS Current
owa.haukeflix.top DNS Current
panel.haukeflix.top DNS Current
partner.haukeflix.top DNS Current
partners.haukeflix.top DNS Current
pay.haukeflix.top DNS Current
payment.haukeflix.top DNS Current
payments.haukeflix.top DNS Current
payroll.haukeflix.top DNS Current
pbx.haukeflix.top DNS Current
phone.haukeflix.top DNS Current
photos.haukeflix.top DNS Current
pki.haukeflix.top DNS Current
plesk.haukeflix.top DNS Current
policies.haukeflix.top DNS Current
policy.haukeflix.top DNS Current
pop.haukeflix.top DNS Current
pop3.haukeflix.top DNS Current
portal.haukeflix.top DNS Current
portal2.haukeflix.top DNS Current
postgres.haukeflix.top DNS Current
pre.haukeflix.top DNS Current
preprod.haukeflix.top DNS Current
press.haukeflix.top DNS Current
preview.haukeflix.top DNS Current
primary.haukeflix.top DNS Current
print.haukeflix.top DNS Current
printer.haukeflix.top DNS Current
privacy.haukeflix.top DNS Current
private.haukeflix.top DNS Current
product.haukeflix.top DNS Current
products.haukeflix.top DNS Current
profile.haukeflix.top DNS Current
prometheus.haukeflix.top DNS Current
promo.haukeflix.top DNS Current
proxy.haukeflix.top DNS Current
proxy1.haukeflix.top DNS Current
proxy2.haukeflix.top DNS Current
public.haukeflix.top DNS Current
qa.haukeflix.top DNS Current
queue.haukeflix.top DNS Current
r.haukeflix.top DNS Current
ra.haukeflix.top DNS Current
rabbitmq.haukeflix.top DNS Current
rancher.haukeflix.top DNS Current
realtime.haukeflix.top DNS Current
recruit.haukeflix.top DNS Current
redirect.haukeflix.top DNS Current
redis.haukeflix.top DNS Current
register.haukeflix.top DNS Current
registry.haukeflix.top DNS Current
relay.haukeflix.top DNS Current
relay1.haukeflix.top DNS Current
releases.haukeflix.top DNS Current
remote.haukeflix.top DNS Current
repo.haukeflix.top DNS Current
report.haukeflix.top DNS Current
reporting.haukeflix.top DNS Current
reports.haukeflix.top DNS Current
repos.haukeflix.top DNS Current
reservations.haukeflix.top DNS Current
rest.haukeflix.top DNS Current
rss.haukeflix.top DNS Current
rt.haukeflix.top DNS Current
s3.haukeflix.top DNS Current
sandbox.haukeflix.top DNS Current
sandbox1.haukeflix.top DNS Current
sandbox2.haukeflix.top DNS Current
scan.haukeflix.top DNS Current
scanner.haukeflix.top DNS Current
schedule.haukeflix.top DNS Current
scp.haukeflix.top DNS Current
search.haukeflix.top DNS Current
secondary.haukeflix.top DNS Current
secrets.haukeflix.top DNS Current
secure.haukeflix.top DNS Current
server.haukeflix.top DNS Current
server1.haukeflix.top DNS Current
server2.haukeflix.top DNS Current
server3.haukeflix.top DNS Current
service.haukeflix.top DNS Current
servicedesk.haukeflix.top DNS Current
services.haukeflix.top DNS Current
sftp.haukeflix.top DNS Current
share.haukeflix.top DNS Current
shop.haukeflix.top DNS Current
signin.haukeflix.top DNS Current
signup.haukeflix.top DNS Current
sip.haukeflix.top DNS Current
slack.haukeflix.top DNS Current
smtp.haukeflix.top DNS Current
smtp1.haukeflix.top DNS Current
smtp2.haukeflix.top DNS Current
socket.haukeflix.top DNS Current
solr.haukeflix.top DNS Current
sql.haukeflix.top DNS Current
srv.haukeflix.top DNS Current
srv1.haukeflix.top DNS Current
srv2.haukeflix.top DNS Current
ssh.haukeflix.top DNS Current
ssl.haukeflix.top DNS Current
sso.haukeflix.top DNS Current
stage.haukeflix.top DNS Current
staging.haukeflix.top DNS Current
static.haukeflix.top DNS Current
static1.haukeflix.top DNS Current
static2.haukeflix.top DNS Current
statistics.haukeflix.top DNS Current
stats.haukeflix.top DNS Current
status.haukeflix.top DNS Current
stg.haukeflix.top DNS Current
storage.haukeflix.top DNS Current
store.haukeflix.top DNS Current
stream.haukeflix.top DNS Current
streaming.haukeflix.top DNS Current
support.haukeflix.top DNS Current
support2.haukeflix.top DNS Current
survey.haukeflix.top DNS Current
surveys.haukeflix.top DNS Current
svc.haukeflix.top DNS Current
svn.haukeflix.top DNS Current
swift.haukeflix.top DNS Current
talent.haukeflix.top DNS Current
teams.haukeflix.top DNS Current
techsupport.haukeflix.top DNS Current
tel.haukeflix.top DNS Current
telecom.haukeflix.top DNS Current
terms.haukeflix.top DNS Current
test.haukeflix.top DNS Current
test1.haukeflix.top DNS Current
test2.haukeflix.top DNS Current
testing.haukeflix.top DNS Current
ticket.haukeflix.top DNS Current
tickets.haukeflix.top DNS Current
tls.haukeflix.top DNS Current
tool.haukeflix.top DNS Current
tools.haukeflix.top DNS Current
trace.haukeflix.top DNS Current
tracing.haukeflix.top DNS Current
tracking.haukeflix.top DNS Current
training.haukeflix.top DNS Current
uat.haukeflix.top DNS Current
upload.haukeflix.top DNS Current
uploads.haukeflix.top DNS Current
uptime.haukeflix.top DNS Current
url.haukeflix.top DNS Current
us-east.haukeflix.top DNS Current
us-west.haukeflix.top DNS Current
us.haukeflix.top DNS Current
utility.haukeflix.top DNS Current
varnish.haukeflix.top DNS Current
vault.haukeflix.top DNS Current
vendor.haukeflix.top DNS Current
vendors.haukeflix.top DNS Current
video.haukeflix.top DNS Current
videos.haukeflix.top DNS Current
voip.haukeflix.top DNS Current
vpn.haukeflix.top DNS Current
vpn1.haukeflix.top DNS Current
vpn2.haukeflix.top DNS Current
vpn3.haukeflix.top DNS Current
vps.haukeflix.top DNS Current
waf.haukeflix.top DNS Current
wan.haukeflix.top DNS Current
warehouse.haukeflix.top DNS Current
web.haukeflix.top DNS Current
web1.haukeflix.top DNS Current
web2.haukeflix.top DNS Current
webex.haukeflix.top DNS Current
webinar.haukeflix.top DNS Current
webinars.haukeflix.top DNS Current
webmail.haukeflix.top DNS Current
websocket.haukeflix.top DNS Current
whm.haukeflix.top DNS Current
wiki.haukeflix.top DNS Current
wordpress.haukeflix.top DNS Current
work.haukeflix.top DNS Current
worker.haukeflix.top DNS Current
worker1.haukeflix.top DNS Current
worker2.haukeflix.top DNS Current
workspace.haukeflix.top DNS Current
wp.haukeflix.top DNS Current
ws.haukeflix.top DNS Current
www.haukeflix.top DNS Current
www1.haukeflix.top DNS Current
www2.haukeflix.top DNS Current
www3.haukeflix.top DNS Current
xml.haukeflix.top DNS Current
zabbix.haukeflix.top DNS Current
zoom.haukeflix.top DNS Current
Δ No Propagation Issues: All DNS records are synchronized between resolver and authoritative nameserver.
DNS Intelligence What does DNS look like right now — and what changed over time?
DNS Evidence Diff Side-by-side comparison
Resolver Records (Public DNS cache)
Authoritative Records (Source of truth)
A Synchronized 1 / 1 records
95.216.5.59
95.216.5.59
AAAA Synchronized 1 / 1 records
2a01:4f9:2a:550::2
2a01:4f9:2a:550::2
CAA RFC 8659 §4 0 / 0 records
No records
No records
DMARC _dmarc.haukeflix.top RFC 7489 §6.3 Synchronized 1 / 1 records
v=DMARC1; p=reject;
v=DMARC1; p=reject;
MX RFC 5321 Synchronized 1 / 1 records
0 .
0 .
NS RFC 1035 Synchronized 4 / 4 records
maceio.ns.porkbun.com.
curitiba.ns.porkbun.com.
salvador.ns.porkbun.com.
fortaleza.ns.porkbun.com.
curitiba.ns.porkbun.com.
maceio.ns.porkbun.com.
fortaleza.ns.porkbun.com.
salvador.ns.porkbun.com.
SOA RFC 1035 Synchronized 1 / 1 records
curitiba.ns.porkbun.com. dns.cloudflare.com. 2398107372 10000 2400 604800 1800
curitiba.ns.porkbun.com. dns.cloudflare.com. 2398107372 10000 2400 604800 1800
TXT RFC 7208 §4 Synchronized 1 / 1 records
v=spf1 -all
v=spf1 -all
DNS History Timeline BETA
Your key is sent directly to SecurityTrails and is never stored on our servers. Get an API key
DNS History Timeline BETA

When was a record added, removed, or changed — and could that change be the problem?

Analyze Another Domain

Confirm Your Email Configuration

This tool analyzes DNS records, but to verify actual email delivery, send a test email to Red Sift Investigate. Their tool shows exactly how your emails arrive, including SPF/DKIM/DMARC pass/fail results in the headers.

DATA FRESHNESS & METHODOLOGY

All security-critical records (SPF, DMARC, DKIM, DANE/TLSA, DNSSEC, MTA-STS, TLS-RPT, BIMI, CAA) are queried live from authoritative nameservers and cross-referenced against 5 independent public DNS resolvers (Cloudflare, Google, Quad9, OpenDNS, DNS4EU) at the time of each analysis. No security verdict uses cached data.

Registrar data (RDAP) is cached for up to 24 hours because domain ownership and registration details change infrequently. Certificate Transparency logs (subdomain discovery via RFC 6962) are cached for 1 hour because CT entries are append-only historical records. Sections using cached data are marked with a CACHED badge; live queries show LIVE.

Intelligence Sources

This analysis used 4 DNS resolvers (consensus), reverse DNS (PTR), Team Cymru (ASN attribution), IANA RDAP (registrar), crt.sh (CT logs), and SMTP probing (transport). All using open-standard protocols.

Full List
Verify Report Integrity SHA-3-512 Has this report been altered since generation? Verify below

This cryptographic hash seals the analysis data, domain, timestamp, and tool version into a tamper-evident fingerprint. Any modification to the report data will produce a different hash. This is distinct from the posture hash (used for drift detection) — the integrity hash uniquely identifies this specific report instance.

d7d509a1e82c31acb47e2f6039e8c75d8260001fdc118f7347e63d4febc052f0dfac1b6adff6f405b772d03f3e839fbdd0154a839f5bbc940abf5eb6fbb51d11
Evaluations reference 12 RFCs. Methods are reproducible using the verification commands provided. Results reflect DNS state at 8 Mar 2026, 01:30 UTC.

Download the intelligence dump and verify its integrity, like you would a Kali ISO or any critical artifact. The SHA-3-512 checksum covers every byte of the download — deterministic serialization ensures identical hashes across downloads.

After downloading, verify with any of these commands:

Tip: cd ~/Downloads first (or wherever you saved the files).

OpenSSL + Sidecar (macOS, Linux, WSL)
cat dns-intelligence-haukeflix.top.json.sha3 && echo '---' && openssl dgst -sha3-512 dns-intelligence-haukeflix.top.json
Python 3 (cross-platform)
python3 -c "import hashlib; print(hashlib.sha3_512(open('dns-intelligence-haukeflix.top.json','rb').read()).hexdigest())"
sha3sum (coreutils 9+)
sha3sum -a 512 dns-intelligence-haukeflix.top.json
Compare the output against the .sha3 file or the checksum API at /api/analysis/6489/checksum. Hash algorithm: SHA-3-512 (Keccak, NIST FIPS 202).

Every finding in this report is backed by DNS queries you can run yourself. These vetted one-liners reproduce the exact checks used to build this report for haukeflix.top. Our analysis adds multi-resolver consensus, RFC-based evaluation, and cross-referencing — but the underlying data is always independently verifiable. We are intelligence analysts, not gatekeepers.

DNS Records

Query A records (IPv4) RFC 1035
dig +noall +answer haukeflix.top A
Query AAAA records (IPv6) RFC 1035
dig +noall +answer haukeflix.top AAAA
Query MX records (mail servers) RFC 1035
dig +noall +answer haukeflix.top MX
Query NS records (nameservers) RFC 1035
dig +noall +answer haukeflix.top NS
Query TXT records RFC 1035
dig +noall +answer haukeflix.top TXT

Email Authentication

Check SPF record RFC 7208
dig +short haukeflix.top TXT | grep -i spf
Check DMARC policy RFC 7489
dig +short _dmarc.haukeflix.top TXT
Check DKIM key for selector 'amazonses' RFC 6376
dig +short amazonses._domainkey.haukeflix.top TXT
Check DKIM key for selector 'barracuda' RFC 6376
dig +short barracuda._domainkey.haukeflix.top TXT
Check DKIM key for selector 'brevo' RFC 6376
dig +short brevo._domainkey.haukeflix.top TXT
Check DKIM key for selector 'cisco' RFC 6376
dig +short cisco._domainkey.haukeflix.top TXT
Check DKIM key for selector 'cm' RFC 6376
dig +short cm._domainkey.haukeflix.top TXT
Check DKIM key for selector 'ctct1' RFC 6376
dig +short ctct1._domainkey.haukeflix.top TXT
Check DKIM key for selector 'ctct2' RFC 6376
dig +short ctct2._domainkey.haukeflix.top TXT
Check DKIM key for selector 'customerio' RFC 6376
dig +short customerio._domainkey.haukeflix.top TXT
Check DKIM key for selector 'default' RFC 6376
dig +short default._domainkey.haukeflix.top TXT
Check DKIM key for selector 'dk' RFC 6376
dig +short dk._domainkey.haukeflix.top TXT
Check DKIM key for selector 'dkim' RFC 6376
dig +short dkim._domainkey.haukeflix.top TXT
Check DKIM key for selector 'dkim1' RFC 6376
dig +short dkim1._domainkey.haukeflix.top TXT
Check DKIM key for selector 'dkim2' RFC 6376
dig +short dkim2._domainkey.haukeflix.top TXT
Check DKIM key for selector 'dkim3' RFC 6376
dig +short dkim3._domainkey.haukeflix.top TXT
Check DKIM key for selector 'drip' RFC 6376
dig +short drip._domainkey.haukeflix.top TXT
Check DKIM key for selector 'em' RFC 6376
dig +short em._domainkey.haukeflix.top TXT
Check DKIM key for selector 'email' RFC 6376
dig +short email._domainkey.haukeflix.top TXT
Check DKIM key for selector 'everlytickey1' RFC 6376
dig +short everlytickey1._domainkey.haukeflix.top TXT
Check DKIM key for selector 'everlytickey2' RFC 6376
dig +short everlytickey2._domainkey.haukeflix.top TXT
Check DKIM key for selector 'fm1' RFC 6376
dig +short fm1._domainkey.haukeflix.top TXT
Check DKIM key for selector 'fm2' RFC 6376
dig +short fm2._domainkey.haukeflix.top TXT
Check DKIM key for selector 'fm3' RFC 6376
dig +short fm3._domainkey.haukeflix.top TXT
Check DKIM key for selector 'freshdesk' RFC 6376
dig +short freshdesk._domainkey.haukeflix.top TXT
Check DKIM key for selector 'google' RFC 6376
dig +short google._domainkey.haukeflix.top TXT
Check DKIM key for selector 'google2048' RFC 6376
dig +short google2048._domainkey.haukeflix.top TXT
Check DKIM key for selector 'hornet' RFC 6376
dig +short hornet._domainkey.haukeflix.top TXT
Check DKIM key for selector 'hs1' RFC 6376
dig +short hs1._domainkey.haukeflix.top TXT
Check DKIM key for selector 'hs2' RFC 6376
dig +short hs2._domainkey.haukeflix.top TXT
Check DKIM key for selector 'hubspot' RFC 6376
dig +short hubspot._domainkey.haukeflix.top TXT
Check DKIM key for selector 'intercom' RFC 6376
dig +short intercom._domainkey.haukeflix.top TXT
Check DKIM key for selector 'k1' RFC 6376
dig +short k1._domainkey.haukeflix.top TXT
Check DKIM key for selector 'k2' RFC 6376
dig +short k2._domainkey.haukeflix.top TXT
Check DKIM key for selector 'k3' RFC 6376
dig +short k3._domainkey.haukeflix.top TXT
Check DKIM key for selector 'key1' RFC 6376
dig +short key1._domainkey.haukeflix.top TXT
Check DKIM key for selector 'key2' RFC 6376
dig +short key2._domainkey.haukeflix.top TXT
Check DKIM key for selector 'klaviyo' RFC 6376
dig +short klaviyo._domainkey.haukeflix.top TXT
Check DKIM key for selector 'mail' RFC 6376
dig +short mail._domainkey.haukeflix.top TXT
Check DKIM key for selector 'mailchimp' RFC 6376
dig +short mailchimp._domainkey.haukeflix.top TXT
Check DKIM key for selector 'mailer' RFC 6376
dig +short mailer._domainkey.haukeflix.top TXT
Check DKIM key for selector 'mailgun' RFC 6376
dig +short mailgun._domainkey.haukeflix.top TXT
Check DKIM key for selector 'mailjet' RFC 6376
dig +short mailjet._domainkey.haukeflix.top TXT
Check DKIM key for selector 'mandrill' RFC 6376
dig +short mandrill._domainkey.haukeflix.top TXT
Check DKIM key for selector 'mandrill2' RFC 6376
dig +short mandrill2._domainkey.haukeflix.top TXT
Check DKIM key for selector 'mc' RFC 6376
dig +short mc._domainkey.haukeflix.top TXT
Check DKIM key for selector 'mimecast' RFC 6376
dig +short mimecast._domainkey.haukeflix.top TXT
Check DKIM key for selector 'ml' RFC 6376
dig +short ml._domainkey.haukeflix.top TXT
Check DKIM key for selector 'mta' RFC 6376
dig +short mta._domainkey.haukeflix.top TXT
Check DKIM key for selector 'mta1' RFC 6376
dig +short mta1._domainkey.haukeflix.top TXT
Check DKIM key for selector 'mta2' RFC 6376
dig +short mta2._domainkey.haukeflix.top TXT
Check DKIM key for selector 'mx' RFC 6376
dig +short mx._domainkey.haukeflix.top TXT
Check DKIM key for selector 'postmark' RFC 6376
dig +short postmark._domainkey.haukeflix.top TXT
Check DKIM key for selector 'proofpoint' RFC 6376
dig +short proofpoint._domainkey.haukeflix.top TXT
Check DKIM key for selector 'protonmail' RFC 6376
dig +short protonmail._domainkey.haukeflix.top TXT
Check DKIM key for selector 'protonmail2' RFC 6376
dig +short protonmail2._domainkey.haukeflix.top TXT
Check DKIM key for selector 'protonmail3' RFC 6376
dig +short protonmail3._domainkey.haukeflix.top TXT
Check DKIM key for selector 's1' RFC 6376
dig +short s1._domainkey.haukeflix.top TXT
Check DKIM key for selector 's2' RFC 6376
dig +short s2._domainkey.haukeflix.top TXT
Check DKIM key for selector 's3' RFC 6376
dig +short s3._domainkey.haukeflix.top TXT
Check DKIM key for selector 'salesforce' RFC 6376
dig +short salesforce._domainkey.haukeflix.top TXT
Check DKIM key for selector 'selector1' RFC 6376
dig +short selector1._domainkey.haukeflix.top TXT
Check DKIM key for selector 'selector2' RFC 6376
dig +short selector2._domainkey.haukeflix.top TXT
Check DKIM key for selector 'selector3' RFC 6376
dig +short selector3._domainkey.haukeflix.top TXT
Check DKIM key for selector 'sendgrid' RFC 6376
dig +short sendgrid._domainkey.haukeflix.top TXT
Check DKIM key for selector 'sendgrid2' RFC 6376
dig +short sendgrid2._domainkey.haukeflix.top TXT
Check DKIM key for selector 'sendinblue' RFC 6376
dig +short sendinblue._domainkey.haukeflix.top TXT
Check DKIM key for selector 'sf1' RFC 6376
dig +short sf1._domainkey.haukeflix.top TXT
Check DKIM key for selector 'sf2' RFC 6376
dig +short sf2._domainkey.haukeflix.top TXT
Check DKIM key for selector 'sig1' RFC 6376
dig +short sig1._domainkey.haukeflix.top TXT
Check DKIM key for selector 'sig2' RFC 6376
dig +short sig2._domainkey.haukeflix.top TXT
Check DKIM key for selector 'smtp' RFC 6376
dig +short smtp._domainkey.haukeflix.top TXT
Check DKIM key for selector 'smtpapi' RFC 6376
dig +short smtpapi._domainkey.haukeflix.top TXT
Check DKIM key for selector 'sparkpost' RFC 6376
dig +short sparkpost._domainkey.haukeflix.top TXT
Check DKIM key for selector 'sq' RFC 6376
dig +short sq._domainkey.haukeflix.top TXT
Check DKIM key for selector 'square' RFC 6376
dig +short square._domainkey.haukeflix.top TXT
Check DKIM key for selector 'squareup' RFC 6376
dig +short squareup._domainkey.haukeflix.top TXT
Check DKIM key for selector 'turbo-smtp' RFC 6376
dig +short turbo-smtp._domainkey.haukeflix.top TXT
Check DKIM key for selector 'zendesk1' RFC 6376
dig +short zendesk1._domainkey.haukeflix.top TXT
Check DKIM key for selector 'zendesk2' RFC 6376
dig +short zendesk2._domainkey.haukeflix.top TXT
Check DKIM key for selector 'zmail' RFC 6376
dig +short zmail._domainkey.haukeflix.top TXT
Check DKIM key for selector 'zoho' RFC 6376
dig +short zoho._domainkey.haukeflix.top TXT
Check DKIM key for selector 'zohomail' RFC 6376
dig +short zohomail._domainkey.haukeflix.top TXT

Domain Security

Check DNSSEC DNSKEY records RFC 4035
dig +dnssec +noall +answer haukeflix.top DNSKEY
Check DNSSEC DS records RFC 4035
dig +noall +answer haukeflix.top DS
Validate DNSSEC chain (requires DNSSEC-validating resolver) RFC 4035
dig +dnssec +cd haukeflix.top A @1.1.1.1

Transport Security

Check TLSA record (replace MX_HOST with actual MX) RFC 7672
dig +noall +answer _25._tcp.MX_HOST TLSA
Check MTA-STS DNS record RFC 8461
dig +short _mta-sts.haukeflix.top TXT
Fetch MTA-STS policy file RFC 8461
curl -sL https://mta-sts.haukeflix.top/.well-known/mta-sts.txt
Check TLS-RPT record RFC 8460
dig +short _smtp._tls.haukeflix.top TXT

Brand & Trust

Check BIMI record BIMI Draft
dig +short default._bimi.haukeflix.top TXT
Check CAA records (certificate authority authorization) RFC 8659
dig +noall +answer haukeflix.top CAA

DNS Records

Check HTTPS/SVCB records RFC 9460
dig +noall +answer haukeflix.top HTTPS

Domain Security

Check CDS/CDNSKEY automation records RFC 7344
dig +noall +answer haukeflix.top CDS

Infrastructure Intelligence

RDAP domain registration lookup RFC 9083
curl -sL 'https://rdap.org/domain/haukeflix.top' | python3 -m json.tool | head -50
Search Certificate Transparency logs RFC 6962
curl -s 'https://crt.sh/?q=%25.haukeflix.top&output=json' | python3 -c "import json,sys; [print(e['name_value']) for e in json.load(sys.stdin)]" | sort -u | head -20
Check security.txt RFC 9116
curl -sL https://haukeflix.top/.well-known/security.txt | head -20

AI Surface

Check for llms.txt
curl -sI https://haukeflix.top/llms.txt | head -5
Check robots.txt for AI crawler rules
curl -s https://haukeflix.top/robots.txt | grep -i -E 'GPTBot|ChatGPT|Claude|Anthropic|Google-Extended|CCBot|PerplexityBot'

Infrastructure Intelligence

ASN lookup for 95.216.5.59 (Team Cymru)
dig +short 59.5.216.95.origin.asn.cymru.com TXT
Commands use dig, openssl, and curl — standard tools available on macOS, Linux, and WSL. Results may vary slightly due to DNS propagation timing and resolver caching.
Intelligence Confidence Audit Engine verified · 9/9 Evaluated
How confident are these results? Each protocol is independently verified against RFC standards. No self-awarded badges.
SPF
Verified 4895 runs
DKIM
Verified 4713 runs
DMARC
Verified 4878 runs
DANE/TLSA
Verified 4697 runs
DNSSEC
Verified 4876 runs
BIMI
Verified 4712 runs
MTA-STS
Verified 4715 runs
TLS-RPT
Verified 4717 runs
CAA
Verified 4709 runs
Maturity: Development Verified Consistent Gold Gold Master
Running Multi-Source Intelligence Audit

haukeflix.top

0s
DNS records — Cloudflare, Google, Quad9, OpenDNS, DNS4EU
Email auth — SPF, DMARC, DKIM selectors
DNSSEC chain of trust & DANE/TLSA
Certificate Transparency & subdomain discovery
SMTP transport & STARTTLS verification
MTA-STS, TLS-RPT, BIMI, CAA
Registrar & infrastructure analysis
Intelligence Classification & Interpretation

Every result includes terminal commands you can run to independently verify the underlying data. No proprietary magic.