Skip to main content
DNS Tool
Engineer's DNS Intelligence Report
Generated 8 Mar 2026, 03:10 UTC
Duration 60.0s
Version v26.35.17
Integrity 17af6ca2abe39c142e5d968d016053e6f94a9076d414165ce61eed56a22fd09d4550d40ed1e1132411a653a6eb32b878247fe8469f09684b7265d0858cd75aa5
Subject Domain
markphd.me

Engineer's DNS Intelligence Report

markphd.me
8 Mar 2026, 03:10 UTC · 60.0s ·v26.35.17 · SHA-3-512: 17af✱✱✱✱ Verify
Executive Methodology
Recon Mode Snapshot Re-analyze New Domain
Footprint
DNS Security & Trust Posture
Risk Level: Critical Risk
2 protocols configured, 7 not configured Why we go beyond letter grades
1 action required 2 recommendations 1 monitoring
Analysis Confidence (ICD 203)
MODERATE 70/100
Resolver agreement is inconsistent for some protocols, limiting confidence. Data currency and system maturity are adequate.
Accuracy 65% Currency 77/100 Maturity verified
Limiting factor: Resolver agreement is low for this scan — some protocols returned inconsistent results across resolvers
Intelligence Currency
Data Currency: Good 77/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
CAA 1 minute (60s) 1 hour (3600s) high CAA TTL is below typical — observed 1 minute (60s), 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 6 hours (21600s) 1 day (86400s) medium NS TTL is below typical — observed 6 hours (21600s), 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.

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 markphd.me
Reference: NIST SP 800-53 SI-7 (Information Integrity) · RFC 8767 (Serve Stale) · RFC 1035 §3.2.1 (TTL semantics) Note: Some DNS providers (e.g., AWS Route 53 alias records, Cloudflare proxied records) enforce fixed TTLs that cannot be modified. If a finding targets a record you cannot edit, it reflects the observed value rather than a configuration error on your part.
Primary NS ns1.vercel-dns.com
Serial 1655722600
Admin hostmaster.nsone.net
Provider Unknown
Timer Value RFC 1912 Range
Refresh43200s1,200–43,200s (20 min – 12 hrs)
Retry7200sFraction of Refresh
Expire1209600s1,209,600–2,419,200s (14–28 days)
Minimum (Neg. Cache)600s300–86,400s (5 min – 1 day)
All SOA timer values are within RFC 1912 recommended ranges.
Email Spoofing
Vulnerable
Brand Impersonation
Not Setup
DNS Tampering
Unsigned
Certificate Control
Configured
Action Required
No SPF and no DMARC — domain is completely unprotected against email spoofing. Both protocols are RFC-recommended (not mandatory), but their absence leaves the domain open to impersonation (CVE-2024-7208, CVE-2024-49040)
Recommended
Publish an SPF record to authorize legitimate mail senders, Publish a DMARC record starting with p=none and rua reporting
Monitoring
DKIM signing inferred from provider — could not directly verify selector
Configured
DKIM (inferred via Unknown), CAA
Not Configured
SPF, DMARC, MTA-STS, TLS-RPT, BIMI, DANE, DNSSEC
Priority Actions Achievable posture: Low Risk
High Add DMARC Reject for No-Mail Domain

This domain has no MX records and appears to be a website-only domain. A DMARC reject policy tells receiving mail servers to reject any email claiming to be from your domain.

Instructs receiving servers to reject all email from this domain — no legitimate mail is expected.
TypeTXT
Host_dmarc.markphd.me
Valuev=DMARC1; p=reject; sp=reject; adkim=s; aspf=s;
RFC 7489
High Lock Down SPF for No-Mail Domain

This domain has no MX records and appears to be a website-only domain. Publishing a strict SPF record explicitly declares that no servers are authorized to send email, preventing attackers from spoofing your domain.

Explicitly declares no servers are authorized to send email from this domain.
TypeTXT
Hostmarkphd.me
Valuev=spf1 -all
RFC 7208
Medium Enable DNSSEC

DNSSEC is not enabled for this domain. DNSSEC provides cryptographic authentication of DNS responses, preventing cache poisoning and DNS spoofing attacks.

RFC 4035
Registrar (RESTRICTED) LIVE
Registry Restricted
.me restricts public WHOIS
Email Service Provider
Unknown
Unprotected
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? Yes no SPF or DMARC protection

SPF Record RFC 7208 §4 Verified

Does this domain declare who may send email on its behalf? No
Warning

No SPF record found

RFC Stance: RFC 7208 defines the SPF mechanism for domains that choose to publish sender authorization. The standard does not mandate SPF publication — it is a voluntary security control.
Operational Security: We flag its absence because any server on the internet can send email claiming to be this domain. Attackers send from a domain — they do not need the domain to have email infrastructure.
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? No policy published
Warning

No DMARC record found

RFC Stance: RFC 7489 is classified as Informational (not Standards Track). DMARC is a widely adopted industry practice but is not an IETF-mandated standard.
Operational Security: Without DMARC, receiving mail servers have no policy for handling SPF/DKIM failures. Spoofed messages may be delivered to recipients.
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
Not Discoverable

DKIM not discoverable via common selectors (large providers use rotating selectors)

RFC 6376 (Provider-Managed) — DKIM signing managed by the detected mail provider per RFC 6376.
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 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 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 MX records available — 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? Yes No DMARC policy (RFC 7489) — attackers can send email appearing to be from this domain with no sender-authentication barrier

BIMI BIMI Spec Verified Warning

Is the brand identity verified and displayed in inboxes? No

No BIMI record found

CAA RFC 8659 §4 Verified Success

Does this domain restrict who can issue TLS certificates? Yes

CAA configured - only pki.goog, Let's Encrypt, Sectigo can issue certificates

Authorized CAs: pki.goog Let's Encrypt Sectigo
0 issue "pki.goog"
0 issue "letsencrypt.org"
0 issue "sectigo.com"
Since September 2025, all public CAs must verify domain control from multiple geographic locations (Multi-Perspective Issuance Corroboration, CA/B Forum Ballot SC-067). CAA records are now checked from multiple network perspectives before certificate issuance.
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 significant AI surface findings

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? No directives
No robots.txt found
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
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 (9)
  • https://markphd.me/
  • https://markphd.me/_next/static/chunks/polyfills-c67a75d1b6f99dc8.js
  • https://markphd.me/_next/static/chunks/webpack-8fa1640cc84ba8fe.js
  • https://markphd.me/_next/static/chunks/framework-5429a50ba5373c56.js
  • https://markphd.me/_next/static/chunks/main-fe015bc011991627.js
  • https://markphd.me/_next/static/chunks/pages/_app-7f290395dab45a0e.js
  • https://markphd.me/_next/static/chunks/548-f9f2c9016f3c303a.js
  • https://markphd.me/_next/static/chunks/pages/index-6b0ef74393268938.js
  • https://markphd.me/_next/static/3CMC1esPiyb6L1nuewVol/_buildManifest.js
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 ns1.vercel-dns.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: ns1.vercel-dns.com, ns2.vercel-dns.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

Glue Record Completeness Complete

NameserverIn-BailiwickIPv4 GlueIPv6 GlueStatus
ns1.vercel-dns.com No N/A N/A OK
ns2.vercel-dns.com No N/A N/A OK

NS TTL Comparison Drift

Child TTL: 86400s Drift: 0s

SOA Serial Consistency Consistent

ns1.vercel-dns.com: 1.6557226e+09
ns2.vercel-dns.com: 1.6557226e+09
Nameserver Fleet Matrix Healthy

Analyzed 2 nameserver(s) for markphd.me — Per-nameserver reachability, ASN diversity, SOA serial sync, and lame delegation checks.

Nameserver IPv4 IPv6 ASN / Operator UDP TCP AA SOA Serial
ns2.vercel-dns.com 198.51.45.13 2a00:edc0:6259:7:13::2 AS62597 1655722600
ns1.vercel-dns.com 198.51.44.13 2620:4d:4000:6259:7:13:0:1 AS62597 1655722600
Unique ASNs
1
Unique Operators
0
Unique /24 Prefixes
2
Diversity Score
Fair

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

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 0 unique ASN(s) across 2 IP address(es)

IPv4 Mappings:
76.76.21.93 → AS ()
76.76.21.98 → AS ()

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? Possible DNSSEC is not deployed, DNS responses are not cryptographically verified

DNSSEC RFC 4033 §2 Verified Unsigned

DNSSEC not configured - DNS responses are unsigned

Domain does not use DNSSEC. Enable in your registrar's DNS settings (look for "DNSSEC" or "DS records" section).

NS Delegation Verified

2 nameserver(s) configured

Nameservers: ns1.vercel-dns.com ns2.vercel-dns.com
Multi-Resolver Verification Recon: Discrepancy detected - Some resolvers returned different results (3 differences found)
Resolver Differences:
A: Cloudflare returned different results: [76.76.21.123 76.76.21.61]
A: Google returned different results: [66.33.60.35 76.76.21.142]
A: DNS4EU returned different results: [66.33.60.129 76.76.21.93]
This may indicate DNS propagation in progress or geo-based DNS routing.
Traffic & Routing Where does this domain's traffic actually terminate?

AIPv4 Address

76.76.21.93
76.76.21.98
Where the domain points for web traffic

AAAAIPv6 Address

No AAAA records
IPv6 not configured

MXMail Servers

No MX records
Domain cannot receive email

SRVServices

No SRV records
No service-specific routing configured
Web: Reachable (2 IPv4, 0 IPv6) Mail: Not configured 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?
1 unique certificates 486 current 0 expired 1 CNAME Source: Certificate Transparency + DNS Intelligence
Subdomains discovered via CT logs (RFC 6962), DNS probing of common service names, and CNAME chain traversal.
Wildcard certificate detected: *.markphd.me Active 1 cert 1 CA: Let's Encrypt
No explicit SANs found on wildcard certificates. Subdomains covered by this wildcard won't appear individually in CT logs (RFC 6962).
DNS probing and CNAME chain traversal were used to discover additional subdomains below.
Certificate Authority Diversity (1 CA observed across CT log history)
Certificate Authority Certs First Issued Last Issued Status
Let's Encrypt 1 2026-01-25 2026-01-25 Active
Subdomain Source Status Provider / CNAME Certificates First Seen Issuer(s)
a.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
academy.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
account.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
accounting.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
accounts.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
ad.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
adfs.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
admin.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
admin1.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
admin2.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
alert.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
alerts.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
alpha.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
analytics.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
ap-south.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
ap.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
apac.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
api.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
api1.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
api2.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
api3.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
apigw.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
apis.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
apm.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
app.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
app1.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
app2.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
appointments.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
apps.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
archive.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
archives.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
asia.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
assets.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
atom.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
auth.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
auth0.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
autoconfig.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
autodiscover.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
b.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
backup.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
backup1.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
backup2.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
beta.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
bi.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
bigdata.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
billing.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
bitbucket.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
blob.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
blog.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
booking.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
broker.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
bucket.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
build.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
builds.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
c.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
ca.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
cache.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
cal.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
calendar.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
campaign.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
campaigns.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
careers.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
cart.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
catalog.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
cd.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
cdn.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
cdn1.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
cdn2.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
cdn3.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
cert.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
certs.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
chat.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
checkout.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
ci.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
client.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
clients.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
cloud.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
cms.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
cname.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
code.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
community.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
compliance.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
conference.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
config.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
configuration.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
confluence.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
connect.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
console.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
containers.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
content.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
corp.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
corporate.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
courses.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
cpanel.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
crl.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
crm.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
d.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
dashboard.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
data.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
data1.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
data2.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
database.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
datadog.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
db.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
db1.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
db2.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
dedicated.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
demo.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
deploy.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
deployment.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
dev.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
dev1.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
dev2.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
develop.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
developer.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
developers.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
devices.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
directory.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
discuss.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
discussions.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
dns.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
dns1.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
dns2.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
doc.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
docker.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
docs.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
documentation.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
download.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
downloads.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
drupal.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
e.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
ecommerce.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
edge.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
edge1.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
edge2.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
education.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
elastic.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
elasticsearch.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
email.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
emea.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
endpoint.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
erp.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
es.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
etl.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
eu-west.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
eu.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
event.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
events.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
exchange.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
ext.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
f.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
faq.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
feed.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
feedback.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
feeds.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
file.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
files.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
finance.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
firewall.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
forms.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
forum.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
forums.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
ftp.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
ftp1.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
ftp2.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
fw.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
gateway.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
geo.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
gis.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
git.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
github.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
gitlab.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
go.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
grafana.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
graphql.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
gw.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
gw1.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
gw2.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
haproxy.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
health.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
healthcheck.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
help.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
helpdesk.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
hiring.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
host.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
hosting.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
hq.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
hr.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
hris.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
hub.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
id.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
identity.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
image.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
images.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
imap.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
img.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
int.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
internal.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
intranet.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
inventory.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
investor.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
investors.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
invoice.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
ir.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
it.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
itsm.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
itsupport.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
jenkins.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
jira.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
jobs.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
k8s.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
kafka.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
kb.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
kibana.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
kong.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
kubernetes.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
lab.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
labs.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
lan.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
lb.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
ldap.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
learn.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
learning.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
legal.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
link.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
links.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
live.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
lms.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
loadbalancer.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
location.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
log.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
login.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
logs.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
m.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
mail.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
mail1.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
mail2.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
mail3.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
manage.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
management.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
manager.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
map.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
maps.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
marketing.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
mdm.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
media.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
meet.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
meeting.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
memcached.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
metrics.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
microservices.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
mobile.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
mongo.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
mongodb.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
monitor.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
monitoring.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
mq.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
mta.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
mx.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
mx1.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
mx2.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
mx3.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
mx4.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
mx5.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
my.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
myaccount.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
mysql.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
na.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
nagios.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
net.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
network.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
news.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
nginx.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
node1.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
node2.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
node3.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
notifications.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
notify.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
ns.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
ns1.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
ns2.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
ns3.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
ns4.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
ns5.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
ns6.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
o365.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
oauth.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
object.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
ocsp.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
office.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
okta.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
order.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
orders.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
origin.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
origin1.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
origin2.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
outlook.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
owa.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
panel.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
partner.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
partners.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
pay.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
payment.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
payments.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
payroll.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
pbx.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
phone.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
photos.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
pki.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
plesk.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
policies.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
policy.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
pop.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
pop3.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
portal.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
portal2.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
postgres.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
pre.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
preprod.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
press.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
preview.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
primary.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
print.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
printer.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
privacy.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
private.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
product.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
products.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
profile.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
prometheus.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
promo.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
proxy.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
proxy1.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
proxy2.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
public.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
qa.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
queue.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
r.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
ra.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
rabbitmq.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
rancher.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
realtime.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
recruit.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
redirect.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
redis.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
register.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
registry.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
relay.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
relay1.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
releases.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
remote.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
repo.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
report.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
reporting.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
reports.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
repos.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
reservations.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
rest.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
rss.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
rt.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
s3.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
sandbox.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
sandbox1.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
sandbox2.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
scan.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
scanner.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
schedule.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
scp.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
search.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
secondary.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
secrets.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
secure.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
server.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
server1.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
server2.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
server3.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
service.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
servicedesk.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
services.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
sftp.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
share.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
shop.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
signin.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
signup.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
sip.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
slack.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
smtp.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
smtp1.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
smtp2.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
socket.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
solr.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
sql.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
srv.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
srv1.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
srv2.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
ssh.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
ssl.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
sso.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
stage.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
staging.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
static.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
static1.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
static2.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
statistics.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
stats.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
status.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
stg.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
storage.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
store.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
stream.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
streaming.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
support.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
support2.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
survey.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
surveys.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
svc.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
svn.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
swift.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
talent.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
teams.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
techsupport.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
tel.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
telecom.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
terms.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
test.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
test1.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
test2.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
testing.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
ticket.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
tickets.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
tls.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
tool.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
tools.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
trace.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
tracing.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
tracking.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
training.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
uat.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
upload.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
uploads.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
uptime.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
url.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
us-east.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
us-west.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
us.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
utility.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
varnish.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
vault.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
vendor.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
vendors.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
video.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
videos.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
voip.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
vpn.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
vpn1.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
vpn2.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
vpn3.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
vps.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
waf.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
wan.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
warehouse.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
web.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
web1.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
web2.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
webex.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
webinar.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
webinars.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
webmail.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
websocket.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
whm.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
wiki.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
wordpress.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
work.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
worker.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
worker1.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
worker2.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
workspace.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
wp.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
ws.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
www.markphd.me DNS Current markphd.me 1 2026-01-25 Let's Encrypt
www1.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
www2.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
www3.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
xml.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
zabbix.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
zoom.markphd.me DNS Current — 1 2026-01-25 Let's Encrypt
Export Recon (CSV)
Δ Changes Detected: A Resolver ≠ Authoritative (TTL / CDN rotation / recent change)
Risk: Low - typically resolves within TTL
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 Propagating 2 / 2 records
76.76.21.93
66.33.60.194
76.76.21.98
76.76.21.93
AAAA 0 / 0 records
No records
No records
CAA RFC 8659 §4 Synchronized 3 / 3 records
0 issue "pki.goog"
0 issue "letsencrypt.org"
0 issue "letsencrypt.org"
0 issue "pki.goog"
0 issue "sectigo.com"
0 issue "sectigo.com"
MX RFC 5321 0 / 0 records
No records
No records
NS RFC 1035 Synchronized 2 / 2 records
ns2.vercel-dns.com.
ns1.vercel-dns.com.
ns1.vercel-dns.com.
ns2.vercel-dns.com.
SOA RFC 1035 Synchronized 1 / 1 records
ns1.vercel-dns.com. hostmaster.nsone.net. 1655722600 43200 7200 1209600 600
ns1.vercel-dns.com. hostmaster.nsone.net. 1655722600 43200 7200 1209600 600
TXT RFC 7208 §4 0 / 0 records
No records
No records
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.

17af6ca2abe39c142e5d968d016053e6f94a9076d414165ce61eed56a22fd09d4550d40ed1e1132411a653a6eb32b878247fe8469f09684b7265d0858cd75aa5
Evaluations reference 12 RFCs. Methods are reproducible using the verification commands provided. Results reflect DNS state at 8 Mar 2026, 03:10 UTC.
Download Raw Intelligence Download Checksum (.sha3)

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-markphd.me.json.sha3 && echo '---' && openssl dgst -sha3-512 dns-intelligence-markphd.me.json
Python 3 (cross-platform) 
python3 -c "import hashlib; print(hashlib.sha3_512(open('dns-intelligence-markphd.me.json','rb').read()).hexdigest())"
sha3sum (coreutils 9+) 
sha3sum -a 512 dns-intelligence-markphd.me.json
Compare the output against the .sha3 file or the checksum API at /api/analysis/6530/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 markphd.me. 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 markphd.me A
Query AAAA records (IPv6) RFC 1035 
dig +noall +answer markphd.me AAAA
Query MX records (mail servers) RFC 1035 
dig +noall +answer markphd.me MX
Query NS records (nameservers) RFC 1035 
dig +noall +answer markphd.me NS
Query TXT records RFC 1035 
dig +noall +answer markphd.me TXT

Email Authentication

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

Domain Security

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

Brand & Trust

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

DNS Records

Check HTTPS/SVCB records RFC 9460 
dig +noall +answer markphd.me HTTPS

Domain Security

Check CDS/CDNSKEY automation records RFC 7344 
dig +noall +answer markphd.me CDS

Infrastructure Intelligence

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

AI Surface

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

Infrastructure Intelligence

ASN lookup for 76.76.21.93 (Team Cymru) 
dig +short 93.21.76.76.origin.asn.cymru.com TXT
ASN lookup for 76.76.21.98 (Team Cymru) 
dig +short 98.21.76.76.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 4898 runs
DKIM
Verified 4716 runs
DMARC
Verified 4881 runs
DANE/TLSA
Verified 4700 runs
DNSSEC
Verified 4879 runs
BIMI
Verified 4715 runs
MTA-STS
Verified 4718 runs
TLS-RPT
Verified 4720 runs
CAA
Verified 4712 runs
Maturity: Development → Verified → Consistent → Gold → Gold Master

Appendix: Verification Commands

The core DNS queries behind this report can be independently verified using these standard terminal commands (dig, openssl, curl). DNS Tool adds multi-resolver consensus, RFC-based evaluation, and cross-referencing on top of the raw data shown here.

DNS Records

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

Email Authentication

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

Domain Security

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

Brand & Trust

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

DNS Records

Check HTTPS/SVCB records (RFC 9460) 
dig +noall +answer markphd.me HTTPS

Domain Security

Check CDS/CDNSKEY automation records (RFC 7344) 
dig +noall +answer markphd.me CDS

Infrastructure Intelligence

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

AI Surface

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

Infrastructure Intelligence

ASN lookup for 76.76.21.93 (Team Cymru) 
dig +short 93.21.76.76.origin.asn.cymru.com TXT
ASN lookup for 76.76.21.98 (Team Cymru) 
dig +short 98.21.76.76.origin.asn.cymru.com TXT
Running Multi-Source Intelligence Audit

markphd.me

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.