Skip to main content
You are analyzing the subdomain pq.resolutionscope.com. Analyze the root domain resolutionscope.com instead?
Email Security Scope: SPF: No Local Record DMARC: Inherited from resolutionscope.com
This subdomain has no locally configured email security records. DMARC protection is inherited from the organizational domain (resolutionscope.com) per RFC 7489 §6.6.3. Analyzing resolutionscope.com shows the organizational domain’s full email security posture.

Engineer's DNS Intelligence Report

pq.resolutionscope.com
6 Nov 2026, 17:04 UTC · 0.0s ·v26.51.0-146-ge5892c0ab · SHA-3-512: ae6b✱✱✱✱ Verify ·Cross-Referenced
Engineer workspace · evidence preserved

Read the verdict first. Descend only as far as the incident requires.

This report keeps the complete technical record while separating decision, interpretation, evidence, and raw reproduction into a stable disclosure gradient.

L0PostureL1InterpretationL2EvidenceL3Raw & reproduce
Hurry path
KEYBOARD !1@2#3$4%5^6 jump to that section · esc back to the verdict

DNS Resolution Failure

DNS resolution failed for this domain — its authoritative nameservers returned SERVFAIL or did not respond. The domain may be registered but its DNS is temporarily unreachable (for example, mid-migration between providers). This is not a confirmation that the domain is unregistered; please re-run the scan shortly.

What This Means

  • The domain's authoritative nameservers returned SERVFAIL or did not respond
  • This is a transient resolution failure — not a confirmation that the domain is unregistered
  • A common cause is a domain mid-migration between DNS providers
  • Security posture cannot be evaluated until DNS resolves — please re-run the scan shortly
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.

ae6bacf67b2b827a7af5aeceb306ca790af881b6363f910d8513a6e8f3afe12bffffefab96bfa98bbdf509448dab04fcdc09b4b9d002b4b07e2a388f9730ef57
Evaluations reference 12 RFCs. Methods are reproducible using the verification commands provided. Results reflect DNS state at 6 Nov 2026, 17:04 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-pq.resolutionscope.com.json.sha3 && echo '---' && openssl dgst -sha3-512 dns-intelligence-pq.resolutionscope.com.json
Python 3 (cross-platform)
python3 -c "import hashlib; print(hashlib.sha3_512(open('dns-intelligence-pq.resolutionscope.com.json','rb').read()).hexdigest())"
sha3sum (coreutils 9+)
sha3sum -a 512 dns-intelligence-pq.resolutionscope.com.json
Compare the output against the .sha3 file or the checksum API at /api/analysis/19397/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 pq.resolutionscope.com. 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 pq.resolutionscope.com A
Query AAAA records (IPv6) RFC 1035
dig +noall +answer pq.resolutionscope.com AAAA
Query MX records (mail servers) RFC 1035
dig +noall +answer pq.resolutionscope.com MX
Query NS records (nameservers) RFC 1035
dig +noall +answer pq.resolutionscope.com NS
Query TXT records RFC 1035
dig +noall +answer pq.resolutionscope.com TXT

Email Authentication

Check SPF record RFC 7208
dig +short pq.resolutionscope.com TXT | grep -i spf
Check DMARC policy RFC 7489
dig +short _dmarc.pq.resolutionscope.com TXT
Check DKIM key for selector 'default' RFC 6376
dig +short default._domainkey.pq.resolutionscope.com TXT
Check DKIM key for selector 'google' RFC 6376
dig +short google._domainkey.pq.resolutionscope.com TXT
Check DKIM key for selector 'selector1' RFC 6376
dig +short selector1._domainkey.pq.resolutionscope.com TXT
Check DKIM key for selector 'selector2' RFC 6376
dig +short selector2._domainkey.pq.resolutionscope.com TXT

Domain Security

Check DNSSEC DNSKEY records RFC 4035
dig +dnssec +noall +answer pq.resolutionscope.com DNSKEY
Check DNSSEC DS records RFC 4035
dig +noall +answer pq.resolutionscope.com DS
Validate DNSSEC chain (requires DNSSEC-validating resolver) RFC 4035
dig +dnssec +cd pq.resolutionscope.com 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.pq.resolutionscope.com TXT
Fetch MTA-STS policy file RFC 8461
curl -sL https://mta-sts.pq.resolutionscope.com/.well-known/mta-sts.txt
Check TLS-RPT record RFC 8460
dig +short _smtp._tls.pq.resolutionscope.com TXT

Brand & Trust

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

DNS Records

Check HTTPS/SVCB records RFC 9460
dig +noall +answer pq.resolutionscope.com HTTPS

Domain Security

Check CDS/CDNSKEY automation records RFC 7344
dig +noall +answer pq.resolutionscope.com CDS

Infrastructure Intelligence

RDAP domain registration lookup RFC 9083
curl -sL 'https://rdap.org/domain/pq.resolutionscope.com' | python3 -m json.tool | head -50
Search Certificate Transparency logs RFC 6962
curl -s 'https://crt.sh/?q=%25.pq.resolutionscope.com&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://pq.resolutionscope.com/.well-known/security.txt | head -20

AI Surface

Check for llms.txt
curl -sI https://pq.resolutionscope.com/llms.txt | head -5
Check robots.txt for AI crawler rules
curl -s https://pq.resolutionscope.com/robots.txt | grep -i -E 'GPTBot|ChatGPT|Claude|Anthropic|Google-Extended|CCBot|PerplexityBot'
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 Gold · 9/9 Evaluated
How confident are these results? Each protocol is independently verified against RFC standards. No self-awarded badges.
SPF
Gold 15673 runs
DKIM
Gold 15463 runs
DMARC
Gold 15654 runs
DANE/TLSA
Gold 15445 runs
DNSSEC
Gold 15632 runs
BIMI
Gold 15460 runs
MTA-STS
Gold 15481 runs
TLS-RPT
Gold 15496 runs
CAA
Gold 15493 runs
Maturity: Development → Verified → Consistent → Gold → Gold Master

0s

Running Real-Time Scan Telemetry

Most scans complete in less than one minute. Some may take longer.

Markers represent known resolver locations. Anycast routing selects the nearest node — exact routing is internal to each provider.

Pipeline nodes reflect live data as each analysis phase completes.

Telemetry Log 0 polls