Skip to main content
DNS Tool
Engineer's DNS Intelligence Report
Generated 3 Apr 2026, 06:01 UTC
Duration 14.1s
Version v26.40.34
Integrity bb87120cc885ae0eaeb13cbb8dbd43435b37f2adbed3a5b88bce191718f22a9cc85ecf94e74e228ae1df1252e4201a58fe97bdf96a14f26928806da1169545b3
Subject Domain
evdnetworks.com

Engineer's DNS Intelligence Report

evdnetworks.com
3 Apr 2026, 06:01 UTC · 14.1s ·v26.40.34 · SHA-3-512: bb87✱✱✱✱ Verify ·Archived ·Cross-Referenced
Executive Topology
Recon Mode Snapshot Re-analyze New Domain
Footprint Microsoft 365
DNS Security & Trust Posture
Risk Level: Medium Risk
3 protocols configured, 5 not configured, 1 unavailable on provider Domain appears to be in deliberate DMARC monitoring phase with aggregate reporting enabled Why we go beyond letter grades
1 recommendation 2 monitoring
Resolver agreement is inconsistent for some protocols, limiting confidence. Data currency and system maturity are adequate.
Accuracy 68% Currency 81/100 Maturity consistent
Limiting factor: Resolver agreement is low for this scan — some protocols returned inconsistent results across resolvers
Currentness Excellent TTL Compliance Excellent Completeness Degraded Source Credibility Excellent TTL Relevance Adequate
ICuAE Details
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
MX 1724s 1 hour (3600s) medium MX TTL is below typical — observed 1724s, 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-7 relevance guidance. Use the TTL Tuner for profile-specific recommendations.
TXT 1725s 1 hour (3600s) medium TXT TTL is below typical — observed 1725s, 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-7 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-7 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 evdnetworks.com
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 a.ns.interland.net
Serial 2024051840
Admin hostmaster.interland.net
Provider Unknown
Timer Value RFC 1912 Range
Refresh1800s1,200–43,200s (20 min – 12 hrs)
Retry900sFraction of Refresh
Expire864000s1,209,600–2,419,200s (14–28 days)
Minimum (Neg. Cache)2560s300–86,400s (5 min – 1 day)
Expire: SOA Expire is 10 days (864000s). 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 10 days (864000s).
RFC 1912 §2.2
Suggested Scanner Configuration High Confidence
Based on 14 historical scans of this domain
Parameter Current Suggested Severity Rationale
timeout_seconds 5s 8s low Average scan duration is 31.4s, suggesting DNS responses are slow for this domain. Increasing timeout from 5s to 8s prevents premature resolution failures.
RFC 8767
Suggestions require explicit approval before applying. No automatic changes will be made.
Email Spoofing
Partial
Brand Impersonation
Not Setup
DNS Tampering
Unsigned
Certificate Control
Open
Recommended
Move DMARC policy from 'none' to 'quarantine' or 'reject'
Monitoring
DMARC record has configuration warnings — review recommended, DKIM signing inferred from provider — could not directly verify selector
Configured
SPF (hard fail), DMARC (with warnings), DKIM (inferred via Microsoft 365)
Not Configured
MTA-STS, TLS-RPT, BIMI, DNSSEC, CAA
Unavailable on Provider
DANE
Priority Actions 5 total Achievable posture: Low Risk
High Upgrade DMARC from p=none

Your DMARC policy is monitor-only (p=none). Upgrade to p=quarantine or p=reject after reviewing reports to actively prevent spoofing.

A quarantine or reject policy instructs receivers to take action on failing mail.
TypeTXT
Host_dmarc.evdnetworks.com (DMARC policy record)
Valuev=DMARC1; p=quarantine; rua=mailto:dmarc-reports@evdnetworks.com
RFC 7489 §6.3
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
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.
TypeCAA
Hostevdnetworks.com (root of domain — adjust CA to match your provider)
Value0 issue "letsencrypt.org"
RFC 8659
Low Add TLS-RPT Reporting

TLS-RPT (TLS Reporting) sends you reports about TLS connection failures when other servers try to deliver mail to your domain.

TLS-RPT sends you reports about TLS connection failures to your mail servers.
TypeTXT
Host_smtp._tls.evdnetworks.com (SMTP TLS reporting record)
Valuev=TLSRPTv1; rua=mailto:tls-reports@evdnetworks.com
RFC 8460
Low Deploy MTA-STS

MTA-STS enforces TLS encryption for inbound mail delivery, preventing downgrade attacks on your mail transport.

MTA-STS tells sending servers to require TLS when delivering mail to your domain.
TypeTXT
Host_mta-sts.evdnetworks.com (MTA-STS policy record)
Valuev=STSv1; id=evdnetworks.com
RFC 8461
Open Remediation Workspace — Copy-Paste Ready Records
Registrar (RDAP) OBSERVED LIVE
Tucows Domains Inc.
Where domain was purchased
Email Service Provider INFERRED
Microsoft 365
Moderately Protected
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 DMARC is monitor-only (p=none)

SPF Record RFC 7208 §4 Consistent

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

SPF valid with strict enforcement (-all), 1/10 lookups

v=spf1 include:spf.protection.outlook.com -all
RFC 7489: -all may cause rejection before DMARC evaluation, preventing DKIM from being checked
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)
SPF hard fail (-all): compliance-strong, but can short-circuit DMARC. RFC 7489 notes that -all can cause some receivers to reject mail during the SMTP transaction — before DKIM is checked and before DMARC can evaluate the result. A message that would pass DMARC via DKIM alignment may be rejected prematurely. For most domains, ~all + DMARC p=reject is the strongest compatible posture — it allows every authentication method (SPF, DKIM, DMARC) to be fully evaluated before a decision is made.
DMARC is monitoring only (p=none). -all provides some SPF-level protection, but DMARC isn't enforcing. Adding p=reject and considering ~all for compatibility would be far more effective.

DMARC Policy RFC 7489 §6.3 Consistent

Are spoofed emails rejected or quarantined? Monitoring only
Warning p=none

DMARC in monitoring mode (p=none) - spoofed mail still delivered, no enforcement

v=DMARC1;p=none;rua=mailto:ee5590a40c@rua.easydmarc.us;ruf=mailto:ee5590a40c@ruf.easydmarc.us;fo=1;
Policy p=none provides no protection - spoofed emails reach inboxes
Forensic reporting (ruf) is configured, but most major providers do not send forensic reports. 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. The DMARCbis draft (draft-ietf-dmarc-dmarcbis) has formally removed ruf= from the specification. Consider removing this tag to simplify your record. RFC 7489 §7.3 — Forensic Reports
Advanced cryptographic posture detected. Domain appears to be in deliberate DMARC monitoring phase with aggregate reporting enabled
RFC 7489 Present — DMARC record published per RFC 7489 §6.3.
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 Consistent

Are outbound emails cryptographically signed? Provider-managed
Provider Verified

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

Microsoft 365 detected as primary mail platform — DKIM signing is managed by the provider. The primary provider may use custom selectors not discoverable through standard checks.
Know your DKIM selector? Re-scan with a custom selector to verify.
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 Consistent

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 Consistent

Will failures in TLS delivery be reported? No reporting
Warning

No TLS-RPT record found

DMARC External Reporting Authorization RFC 7489 §7.1

Are external report receivers authorized? Yes — all authorized
Success

All 2 external reporting domains properly authorized

External Domain Authorization Auth Record
rua.easydmarc.us Authorized v=DMARC1;
ruf.easydmarc.us Authorized v=DMARC1;
DANE / TLSA Consistent Recon Methodology Can mail servers establish identity without a public CA? No
RFC 7672 §3 RFC 6698 §2 Not Available

DANE not available — Microsoft 365 does not support inbound DANE/TLSA on its MX infrastructure

DANE not deployable on Microsoft 365

Microsoft 365 does not support DANE for inbound mail. Microsoft uses its own certificate pinning mechanism.

Recommended alternative: MTA-STS

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. Since Microsoft 365 does not support inbound DANE, deploy MTA-STS (RFC 8461) to enforce TLS and protect against downgrade attacks.

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? Likely DMARC is monitor-only p=none (RFC 7489 §6.3) — spoofed mail is not blocked, brand faking is trivial

BIMI BIMI Spec Consistent Warning

Is the brand identity verified and displayed in inboxes? No

No BIMI record found

CAA RFC 8659 §4 Consistent 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? Risks Found

AI-related risks detected — review recommended

llms.txt llmstxt.org
Is this domain publishing AI-readable brand context? Yes
llms.txt found — domain provides structured context for LLMs View llms.txt
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 View 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? Yes — 2 found
2 hidden prompt artifact(s) found
  • CSS display:none Hidden element with prompt keyword 'override' detected near CSS display:none pattern
  • CSS visibility:hidden Hidden element with prompt keyword 'override' detected near CSS visibility:hidden pattern
Evidence Log (4 items)
TypeDetailSeverityConfidence
llms_txt_found llms.txt file found providing structured LLM context info Observed
robots_txt_no_ai_blocks robots.txt found but no AI-specific blocking directives low Observed
hidden_prompt Hidden element with prompt keyword 'override' detected near CSS display:none pattern high Observed
hidden_prompt Hidden element with prompt keyword 'override' detected near CSS visibility:hidden pattern high 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)
  • http://evdnetworks.com/
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 a.ns.interland.net — 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: a.ns.interland.net, b.ns.interland.net, c.ns.interland.net

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
a.ns.interland.net No N/A N/A OK
b.ns.interland.net No N/A N/A OK
c.ns.interland.net No N/A N/A OK

NS TTL Comparison Drift

Child TTL: 86400s Drift: 0s

SOA Serial Consistency Consistent

a.ns.interland.net: 2.02405184e+09
b.ns.interland.net: 2.02405184e+09
c.ns.interland.net: 2.02405184e+09
Nameserver Fleet Matrix 3 Issues

Analyzed 3 nameserver(s) for evdnetworks.com — Per-nameserver reachability, ASN diversity, SOA serial sync, and lame delegation checks.

Findings:
  • c.ns.interland.net: TCP unreachable on port 53
  • a.ns.interland.net: TCP unreachable on port 53
  • b.ns.interland.net: TCP unreachable on port 53
Nameserver IPv4 IPv6 ASN / Operator UDP TCP AA SOA Serial
c.ns.interland.net 207.204.21.32 None AS19871 2024051840
a.ns.interland.net 162.214.41.49 None AS46606 2024051840
b.ns.interland.net 207.204.21.32 None AS19871 2024051840
Unique ASNs
2
Unique Operators
0
Unique /24 Prefixes
2
Diversity Score
Good

2 ASNs, 2 /24 prefixes across 3 nameservers

Mail Transport Security Beta Is mail transport encrypted and verified? No No MTA-STS or DANE — mail transport encryption is opportunistic only

All 1 server(s) verified: encrypted transport confirmed via direct SMTP probe and DNS policy

Policy Assessment Primary
  • Microsoft 365 enforces TLS 1.2+ with DANE (GA Oct 2024) and valid certificates
Telemetry
TLS-RPT not configured — domain has no visibility into TLS delivery failures from real senders
Live Probe Supplementary
MX Host STARTTLS TLS Version Cipher Certificate
evdnetworks-com.mail.protection.outlook.com TLSv1.3 TLS_AES_256_GCM_SHA384 Valid
Expires: 2026-08-26 (145 days)
Issuer: DigiCert Inc
Multi-Vantage Probe Results
Unanimous: TLS verified 2 probes, 2 responded
US-East (Boston) observed
All servers support TLS
France - EU observed
All servers support TLS
7.432648832s
Infrastructure Intelligence Who hosts this domain and what services power it? Direct

ASN / Network Success

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

ASNNameCountry
AS31898 US
IPv4 Mappings:
205.147.88.159 → AS31898 (205.147.88.0/23)

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 Consistent 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

3 nameserver(s) configured

Nameservers: a.ns.interland.net b.ns.interland.net c.ns.interland.net
Multi-Resolver Verification Recon: Consensus reached - 5 resolvers (Cloudflare, Google, Quad9, OpenDNS, DNS4EU) agree on DNS records
Traffic & Routing Where does this domain's traffic actually terminate?

AIPv4 Address

205.147.88.159
Where the domain points for web traffic

AAAAIPv6 Address

No AAAA records
IPv6 not configured

MXMail Servers

0 evdnetworks-com.mail.protection.outlook.com.
Priority + mail server for email delivery
Microsoft 365

SRVServices

No SRV records
No service-specific routing configured
Web: Reachable (1 IPv4, 0 IPv6) Mail: 1 server Services: None
Subdomain Discovery RFC 6962 Recon LIVE What subdomains and infrastructure are exposed in certificate logs? 511 subdomains discovered
How did we find these?
CT logs unavailable 511 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.
Subdomain Source Status Provider / CNAME Certificates First Seen Issuer(s)
a.evdnetworks.com DNS Current — — — —
academy.evdnetworks.com DNS Current — — — —
account.evdnetworks.com DNS Current — — — —
accounting.evdnetworks.com DNS Current — — — —
accounts.evdnetworks.com DNS Current — — — —
ad.evdnetworks.com DNS Current — — — —
adfs.evdnetworks.com DNS Current — — — —
admin.evdnetworks.com DNS Current — — — —
admin1.evdnetworks.com DNS Current — — — —
admin2.evdnetworks.com DNS Current — — — —
alert.evdnetworks.com DNS Current — — — —
alerts.evdnetworks.com DNS Current — — — —
alpha.evdnetworks.com DNS Current — — — —
analytics.evdnetworks.com DNS Current — — — —
ap-south.evdnetworks.com DNS Current — — — —
ap.evdnetworks.com DNS Current — — — —
apac.evdnetworks.com DNS Current — — — —
api.evdnetworks.com DNS Current — — — —
api1.evdnetworks.com DNS Current — — — —
api2.evdnetworks.com DNS Current — — — —
api3.evdnetworks.com DNS Current — — — —
apigw.evdnetworks.com DNS Current — — — —
apis.evdnetworks.com DNS Current — — — —
apm.evdnetworks.com DNS Current — — — —
app.evdnetworks.com DNS Current — — — —
app1.evdnetworks.com DNS Current — — — —
app2.evdnetworks.com DNS Current — — — —
appointments.evdnetworks.com DNS Current — — — —
apps.evdnetworks.com DNS Current — — — —
archive.evdnetworks.com DNS Current — — — —
archives.evdnetworks.com DNS Current — — — —
asia.evdnetworks.com DNS Current — — — —
assets.evdnetworks.com DNS Current — — — —
atom.evdnetworks.com DNS Current — — — —
auth.evdnetworks.com DNS Current — — — —
auth0.evdnetworks.com DNS Current — — — —
autoconfig.evdnetworks.com DNS Current — — — —
autodiscover.evdnetworks.com DNS Current autodiscover.outlook.com — — —
b.evdnetworks.com DNS Current — — — —
backup.evdnetworks.com DNS Current — — — —
backup1.evdnetworks.com DNS Current — — — —
backup2.evdnetworks.com DNS Current — — — —
beta.evdnetworks.com DNS Current — — — —
bi.evdnetworks.com DNS Current — — — —
bigdata.evdnetworks.com DNS Current — — — —
billing.evdnetworks.com DNS Current — — — —
bitbucket.evdnetworks.com DNS Current — — — —
blob.evdnetworks.com DNS Current — — — —
blog.evdnetworks.com DNS Current — — — —
booking.evdnetworks.com DNS Current — — — —
broker.evdnetworks.com DNS Current — — — —
bucket.evdnetworks.com DNS Current — — — —
build.evdnetworks.com DNS Current — — — —
builds.evdnetworks.com DNS Current — — — —
c.evdnetworks.com DNS Current — — — —
ca.evdnetworks.com DNS Current — — — —
cache.evdnetworks.com DNS Current — — — —
cal.evdnetworks.com DNS Current — — — —
calendar.evdnetworks.com DNS Current — — — —
campaign.evdnetworks.com DNS Current — — — —
campaigns.evdnetworks.com DNS Current — — — —
careers.evdnetworks.com DNS Current — — — —
cart.evdnetworks.com DNS Current — — — —
catalog.evdnetworks.com DNS Current — — — —
cd.evdnetworks.com DNS Current — — — —
cdn.evdnetworks.com DNS Current — — — —
cdn1.evdnetworks.com DNS Current — — — —
cdn2.evdnetworks.com DNS Current — — — —
cdn3.evdnetworks.com DNS Current — — — —
cert.evdnetworks.com DNS Current — — — —
certs.evdnetworks.com DNS Current — — — —
chat.evdnetworks.com DNS Current — — — —
checkout.evdnetworks.com DNS Current — — — —
ci.evdnetworks.com DNS Current — — — —
client.evdnetworks.com DNS Current — — — —
clients.evdnetworks.com DNS Current — — — —
cloud.evdnetworks.com DNS Current — — — —
cms.evdnetworks.com DNS Current — — — —
cname.evdnetworks.com DNS Current — — — —
code.evdnetworks.com DNS Current — — — —
community.evdnetworks.com DNS Current — — — —
compliance.evdnetworks.com DNS Current — — — —
conference.evdnetworks.com DNS Current — — — —
config.evdnetworks.com DNS Current — — — —
configuration.evdnetworks.com DNS Current — — — —
confluence.evdnetworks.com DNS Current — — — —
connect.evdnetworks.com DNS Current — — — —
console.evdnetworks.com DNS Current — — — —
containers.evdnetworks.com DNS Current — — — —
content.evdnetworks.com DNS Current — — — —
corp.evdnetworks.com DNS Current — — — —
corporate.evdnetworks.com DNS Current — — — —
courses.evdnetworks.com DNS Current — — — —
cpanel.evdnetworks.com DNS Current — — — —
crl.evdnetworks.com DNS Current — — — —
crm.evdnetworks.com DNS Current — — — —
d.evdnetworks.com DNS Current — — — —
dashboard.evdnetworks.com DNS Current — — — —
data.evdnetworks.com DNS Current — — — —
data1.evdnetworks.com DNS Current — — — —
data2.evdnetworks.com DNS Current — — — —
database.evdnetworks.com DNS Current — — — —
datadog.evdnetworks.com DNS Current — — — —
db.evdnetworks.com DNS Current — — — —
db1.evdnetworks.com DNS Current — — — —
db2.evdnetworks.com DNS Current — — — —
dedicated.evdnetworks.com DNS Current — — — —
demo.evdnetworks.com DNS Current — — — —
deploy.evdnetworks.com DNS Current — — — —
deployment.evdnetworks.com DNS Current — — — —
dev.evdnetworks.com DNS Current — — — —
dev1.evdnetworks.com DNS Current — — — —
dev2.evdnetworks.com DNS Current — — — —
develop.evdnetworks.com DNS Current — — — —
developer.evdnetworks.com DNS Current — — — —
developers.evdnetworks.com DNS Current — — — —
devices.evdnetworks.com DNS Current — — — —
devops.evdnetworks.com DNS Current — — — —
directory.evdnetworks.com DNS Current — — — —
discuss.evdnetworks.com DNS Current — — — —
discussions.evdnetworks.com DNS Current — — — —
dns.evdnetworks.com DNS Current — — — —
dns1.evdnetworks.com DNS Current — — — —
dns2.evdnetworks.com DNS Current — — — —
dnscheck.evdnetworks.com DNS Current — — — —
dnstool.evdnetworks.com DNS Current — — — —
doc.evdnetworks.com DNS Current — — — —
docker.evdnetworks.com DNS Current — — — —
docs.evdnetworks.com DNS Current — — — —
documentation.evdnetworks.com DNS Current — — — —
download.evdnetworks.com DNS Current — — — —
downloads.evdnetworks.com DNS Current — — — —
drupal.evdnetworks.com DNS Current — — — —
e.evdnetworks.com DNS Current — — — —
ecommerce.evdnetworks.com DNS Current — — — —
edge.evdnetworks.com DNS Current — — — —
edge1.evdnetworks.com DNS Current — — — —
edge2.evdnetworks.com DNS Current — — — —
education.evdnetworks.com DNS Current — — — —
elastic.evdnetworks.com DNS Current — — — —
elasticsearch.evdnetworks.com DNS Current — — — —
email.evdnetworks.com DNS Current — — — —
emea.evdnetworks.com DNS Current — — — —
endpoint.evdnetworks.com DNS Current — — — —
erp.evdnetworks.com DNS Current — — — —
es.evdnetworks.com DNS Current — — — —
etl.evdnetworks.com DNS Current — — — —
eu-west.evdnetworks.com DNS Current — — — —
eu.evdnetworks.com DNS Current — — — —
event.evdnetworks.com DNS Current — — — —
events.evdnetworks.com DNS Current — — — —
exchange.evdnetworks.com DNS Current — — — —
ext.evdnetworks.com DNS Current — — — —
f.evdnetworks.com DNS Current — — — —
faq.evdnetworks.com DNS Current — — — —
feed.evdnetworks.com DNS Current — — — —
feedback.evdnetworks.com DNS Current — — — —
feeds.evdnetworks.com DNS Current — — — —
file.evdnetworks.com DNS Current — — — —
files.evdnetworks.com DNS Current — — — —
finance.evdnetworks.com DNS Current — — — —
firewall.evdnetworks.com DNS Current — — — —
forms.evdnetworks.com DNS Current — — — —
forum.evdnetworks.com DNS Current — — — —
forums.evdnetworks.com DNS Current — — — —
ftp.evdnetworks.com DNS Current — — — —
ftp1.evdnetworks.com DNS Current — — — —
ftp2.evdnetworks.com DNS Current — — — —
fw.evdnetworks.com DNS Current — — — —
gateway.evdnetworks.com DNS Current — — — —
geo.evdnetworks.com DNS Current — — — —
get.evdnetworks.com CT Log Current — — — —
gis.evdnetworks.com DNS Current — — — —
git.evdnetworks.com DNS Current — — — —
github.evdnetworks.com DNS Current — — — —
gitlab.evdnetworks.com DNS Current — — — —
go.evdnetworks.com DNS Current — — — —
grafana.evdnetworks.com DNS Current — — — —
graphql.evdnetworks.com DNS Current — — — —
gw.evdnetworks.com DNS Current — — — —
gw1.evdnetworks.com DNS Current — — — —
gw2.evdnetworks.com DNS Current — — — —
haproxy.evdnetworks.com DNS Current — — — —
health.evdnetworks.com DNS Current — — — —
healthcheck.evdnetworks.com DNS Current — — — —
help.evdnetworks.com DNS Current — — — —
helpdesk.evdnetworks.com DNS Current — — — —
hiring.evdnetworks.com DNS Current — — — —
host.evdnetworks.com DNS Current — — — —
hosting.evdnetworks.com DNS Current — — — —
hq.evdnetworks.com DNS Current — — — —
hr.evdnetworks.com DNS Current — — — —
hris.evdnetworks.com DNS Current — — — —
hub.evdnetworks.com DNS Current — — — —
id.evdnetworks.com DNS Current — — — —
identity.evdnetworks.com DNS Current — — — —
image.evdnetworks.com DNS Current — — — —
images.evdnetworks.com DNS Current — — — —
imap.evdnetworks.com DNS Current — — — —
img.evdnetworks.com DNS Current — — — —
int.evdnetworks.com DNS Current — — — —
internal.evdnetworks.com DNS Current — — — —
intranet.evdnetworks.com DNS Current — — — —
inventory.evdnetworks.com DNS Current — — — —
investor.evdnetworks.com DNS Current — — — —
investors.evdnetworks.com DNS Current — — — —
invoice.evdnetworks.com DNS Current — — — —
ir.evdnetworks.com DNS Current — — — —
it.evdnetworks.com DNS Current — — — —
itsm.evdnetworks.com DNS Current — — — —
itsupport.evdnetworks.com DNS Current — — — —
jenkins.evdnetworks.com DNS Current — — — —
jira.evdnetworks.com DNS Current — — — —
jobs.evdnetworks.com DNS Current — — — —
k8s.evdnetworks.com DNS Current — — — —
kafka.evdnetworks.com DNS Current — — — —
kb.evdnetworks.com DNS Current — — — —
kibana.evdnetworks.com DNS Current — — — —
kong.evdnetworks.com DNS Current — — — —
kubernetes.evdnetworks.com DNS Current — — — —
lab.evdnetworks.com DNS Current — — — —
labs.evdnetworks.com DNS Current — — — —
lan.evdnetworks.com DNS Current — — — —
lb.evdnetworks.com DNS Current — — — —
ldap.evdnetworks.com DNS Current — — — —
learn.evdnetworks.com DNS Current — — — —
learning.evdnetworks.com DNS Current — — — —
legal.evdnetworks.com DNS Current — — — —
link.evdnetworks.com DNS Current — — — —
links.evdnetworks.com DNS Current — — — —
live.evdnetworks.com DNS Current — — — —
lms.evdnetworks.com DNS Current — — — —
loadbalancer.evdnetworks.com DNS Current — — — —
location.evdnetworks.com DNS Current — — — —
log.evdnetworks.com DNS Current — — — —
login.evdnetworks.com DNS Current — — — —
logs.evdnetworks.com DNS Current — — — —
lookup.evdnetworks.com DNS Current — — — —
m.evdnetworks.com DNS Current — — — —
mail.evdnetworks.com DNS Current — — — —
mail1.evdnetworks.com DNS Current — — — —
mail2.evdnetworks.com DNS Current — — — —
mail3.evdnetworks.com DNS Current — — — —
mailgw.evdnetworks.com DNS Current — — — —
mailhost.evdnetworks.com DNS Current — — — —
mailrelay.evdnetworks.com DNS Current — — — —
mailserver.evdnetworks.com DNS Current — — — —
manage.evdnetworks.com DNS Current — — — —
management.evdnetworks.com DNS Current — — — —
manager.evdnetworks.com DNS Current — — — —
map.evdnetworks.com DNS Current — — — —
maps.evdnetworks.com DNS Current — — — —
marketing.evdnetworks.com DNS Current — — — —
mdm.evdnetworks.com DNS Current — — — —
media.evdnetworks.com DNS Current — — — —
meet.evdnetworks.com DNS Current — — — —
meeting.evdnetworks.com DNS Current — — — —
memcached.evdnetworks.com DNS Current — — — —
metrics.evdnetworks.com DNS Current — — — —
microservices.evdnetworks.com DNS Current — — — —
mobile.evdnetworks.com DNS Current — — — —
mongo.evdnetworks.com DNS Current — — — —
mongodb.evdnetworks.com DNS Current — — — —
monitor.evdnetworks.com DNS Current — — — —
monitoring.evdnetworks.com DNS Current — — — —
mq.evdnetworks.com DNS Current — — — —
mta.evdnetworks.com DNS Current — — — —
mx.evdnetworks.com DNS Current — — — —
mx1.evdnetworks.com DNS Current — — — —
mx2.evdnetworks.com DNS Current — — — —
mx3.evdnetworks.com DNS Current — — — —
mx4.evdnetworks.com DNS Current — — — —
mx5.evdnetworks.com DNS Current — — — —
mxtoolbox.evdnetworks.com DNS Current — — — —
my.evdnetworks.com DNS Current — — — —
myaccount.evdnetworks.com DNS Current — — — —
mysql.evdnetworks.com DNS Current — — — —
na.evdnetworks.com DNS Current — — — —
nagios.evdnetworks.com DNS Current — — — —
net.evdnetworks.com DNS Current — — — —
netadmin.evdnetworks.com DNS Current — — — —
nettool.evdnetworks.com DNS Current — — — —
nettools.evdnetworks.com DNS Current — — — —
network.evdnetworks.com DNS Current — — — —
news.evdnetworks.com DNS Current — — — —
nginx.evdnetworks.com DNS Current — — — —
node1.evdnetworks.com DNS Current — — — —
node2.evdnetworks.com DNS Current — — — —
node3.evdnetworks.com DNS Current — — — —
notifications.evdnetworks.com DNS Current — — — —
notify.evdnetworks.com DNS Current — — — —
ns.evdnetworks.com DNS Current — — — —
ns1.evdnetworks.com DNS Current — — — —
ns2.evdnetworks.com DNS Current — — — —
ns3.evdnetworks.com DNS Current — — — —
ns4.evdnetworks.com DNS Current — — — —
ns5.evdnetworks.com DNS Current — — — —
ns6.evdnetworks.com DNS Current — — — —
o365.evdnetworks.com DNS Current — — — —
oauth.evdnetworks.com DNS Current — — — —
object.evdnetworks.com DNS Current — — — —
ocsp.evdnetworks.com DNS Current — — — —
office.evdnetworks.com DNS Current — — — —
okta.evdnetworks.com DNS Current — — — —
order.evdnetworks.com DNS Current — — — —
orders.evdnetworks.com DNS Current — — — —
origin.evdnetworks.com DNS Current — — — —
origin1.evdnetworks.com DNS Current — — — —
origin2.evdnetworks.com DNS Current — — — —
outlook.evdnetworks.com DNS Current — — — —
owa.evdnetworks.com DNS Current — — — —
panel.evdnetworks.com DNS Current — — — —
partner.evdnetworks.com DNS Current — — — —
partners.evdnetworks.com DNS Current — — — —
pay.evdnetworks.com DNS Current — — — —
payment.evdnetworks.com DNS Current — — — —
payments.evdnetworks.com DNS Current — — — —
payroll.evdnetworks.com DNS Current — — — —
pbx.evdnetworks.com DNS Current — — — —
phone.evdnetworks.com DNS Current — — — —
photos.evdnetworks.com DNS Current — — — —
pingdom.evdnetworks.com DNS Current — — — —
pki.evdnetworks.com DNS Current — — — —
plesk.evdnetworks.com DNS Current — — — —
policies.evdnetworks.com DNS Current — — — —
policy.evdnetworks.com DNS Current — — — —
pop.evdnetworks.com DNS Current — — — —
pop3.evdnetworks.com DNS Current — — — —
portal.evdnetworks.com DNS Current — — — —
portal2.evdnetworks.com DNS Current — — — —
postgres.evdnetworks.com DNS Current — — — —
pre.evdnetworks.com DNS Current — — — —
preprod.evdnetworks.com DNS Current — — — —
press.evdnetworks.com DNS Current — — — —
preview.evdnetworks.com DNS Current — — — —
primary.evdnetworks.com DNS Current — — — —
print.evdnetworks.com DNS Current — — — —
printer.evdnetworks.com DNS Current — — — —
privacy.evdnetworks.com DNS Current — — — —
private.evdnetworks.com DNS Current — — — —
product.evdnetworks.com DNS Current — — — —
products.evdnetworks.com DNS Current — — — —
profile.evdnetworks.com DNS Current — — — —
prometheus.evdnetworks.com DNS Current — — — —
promo.evdnetworks.com DNS Current — — — —
proxy.evdnetworks.com DNS Current — — — —
proxy1.evdnetworks.com DNS Current — — — —
proxy2.evdnetworks.com DNS Current — — — —
public.evdnetworks.com DNS Current — — — —
qa.evdnetworks.com DNS Current — — — —
queue.evdnetworks.com DNS Current — — — —
r.evdnetworks.com DNS Current — — — —
ra.evdnetworks.com DNS Current — — — —
rabbitmq.evdnetworks.com DNS Current — — — —
rancher.evdnetworks.com DNS Current — — — —
realtime.evdnetworks.com DNS Current — — — —
recruit.evdnetworks.com DNS Current — — — —
redirect.evdnetworks.com DNS Current — — — —
redis.evdnetworks.com DNS Current — — — —
register.evdnetworks.com DNS Current — — — —
registry.evdnetworks.com DNS Current — — — —
relay.evdnetworks.com DNS Current — — — —
relay1.evdnetworks.com DNS Current — — — —
releases.evdnetworks.com DNS Current — — — —
remote.evdnetworks.com DNS Current — — — —
repo.evdnetworks.com DNS Current — — — —
report.evdnetworks.com DNS Current — — — —
reporting.evdnetworks.com DNS Current — — — —
reports.evdnetworks.com DNS Current — — — —
repos.evdnetworks.com DNS Current — — — —
reservations.evdnetworks.com DNS Current — — — —
rest.evdnetworks.com DNS Current — — — —
rss.evdnetworks.com DNS Current — — — —
rt.evdnetworks.com DNS Current — — — —
s3.evdnetworks.com DNS Current — — — —
sandbox.evdnetworks.com DNS Current — — — —
sandbox1.evdnetworks.com DNS Current — — — —
sandbox2.evdnetworks.com DNS Current — — — —
scan.evdnetworks.com DNS Current — — — —
scanner.evdnetworks.com DNS Current — — — —
schedule.evdnetworks.com DNS Current — — — —
scp.evdnetworks.com DNS Current — — — —
search.evdnetworks.com DNS Current — — — —
secondary.evdnetworks.com DNS Current — — — —
secrets.evdnetworks.com DNS Current — — — —
secure.evdnetworks.com DNS Current — — — —
server.evdnetworks.com DNS Current — — — —
server1.evdnetworks.com DNS Current — — — —
server2.evdnetworks.com DNS Current — — — —
server3.evdnetworks.com DNS Current — — — —
service.evdnetworks.com DNS Current — — — —
servicedesk.evdnetworks.com DNS Current — — — —
services.evdnetworks.com DNS Current — — — —
sftp.evdnetworks.com DNS Current — — — —
share.evdnetworks.com DNS Current — — — —
shop.evdnetworks.com DNS Current — — — —
signin.evdnetworks.com DNS Current — — — —
signup.evdnetworks.com DNS Current — — — —
slack.evdnetworks.com DNS Current — — — —
smtp.evdnetworks.com DNS Current — — — —
smtp1.evdnetworks.com DNS Current — — — —
smtp2.evdnetworks.com DNS Current — — — —
socket.evdnetworks.com DNS Current — — — —
solr.evdnetworks.com DNS Current — — — —
speedtest.evdnetworks.com DNS Current — — — —
sql.evdnetworks.com DNS Current — — — —
srv.evdnetworks.com DNS Current — — — —
srv1.evdnetworks.com DNS Current — — — —
srv2.evdnetworks.com DNS Current — — — —
ssh.evdnetworks.com DNS Current — — — —
ssl.evdnetworks.com DNS Current — — — —
sso.evdnetworks.com DNS Current — — — —
stage.evdnetworks.com DNS Current — — — —
staging.evdnetworks.com DNS Current — — — —
static.evdnetworks.com DNS Current — — — —
static1.evdnetworks.com DNS Current — — — —
static2.evdnetworks.com DNS Current — — — —
statistics.evdnetworks.com DNS Current — — — —
stats.evdnetworks.com DNS Current — — — —
status.evdnetworks.com DNS Current — — — —
statuspage.evdnetworks.com DNS Current — — — —
stg.evdnetworks.com DNS Current — — — —
storage.evdnetworks.com DNS Current — — — —
store.evdnetworks.com DNS Current — — — —
stream.evdnetworks.com DNS Current — — — —
streaming.evdnetworks.com DNS Current — — — —
support.evdnetworks.com DNS Current — — — —
support2.evdnetworks.com DNS Current — — — —
survey.evdnetworks.com DNS Current — — — —
surveys.evdnetworks.com DNS Current — — — —
svc.evdnetworks.com DNS Current — — — —
svn.evdnetworks.com DNS Current — — — —
swift.evdnetworks.com DNS Current — — — —
sysadmin.evdnetworks.com DNS Current — — — —
syslog.evdnetworks.com DNS Current — — — —
talent.evdnetworks.com DNS Current — — — —
teams.evdnetworks.com DNS Current — — — —
techsupport.evdnetworks.com DNS Current — — — —
tel.evdnetworks.com DNS Current — — — —
telecom.evdnetworks.com DNS Current — — — —
terms.evdnetworks.com DNS Current — — — —
test.evdnetworks.com DNS Current — — — —
test1.evdnetworks.com DNS Current — — — —
test2.evdnetworks.com DNS Current — — — —
testing.evdnetworks.com DNS Current — — — —
ticket.evdnetworks.com DNS Current — — — —
tickets.evdnetworks.com DNS Current — — — —
tls.evdnetworks.com DNS Current — — — —
tool.evdnetworks.com DNS Current — — — —
tools.evdnetworks.com DNS Current — — — —
trace.evdnetworks.com DNS Current — — — —
tracing.evdnetworks.com DNS Current — — — —
tracking.evdnetworks.com DNS Current — — — —
training.evdnetworks.com DNS Current — — — —
uat.evdnetworks.com DNS Current — — — —
upload.evdnetworks.com DNS Current — — — —
uploads.evdnetworks.com DNS Current — — — —
uptime.evdnetworks.com DNS Current — — — —
url.evdnetworks.com DNS Current — — — —
us-east.evdnetworks.com DNS Current — — — —
us-west.evdnetworks.com DNS Current — — — —
us.evdnetworks.com DNS Current — — — —
utility.evdnetworks.com DNS Current — — — —
varnish.evdnetworks.com DNS Current — — — —
vault.evdnetworks.com DNS Current — — — —
vendor.evdnetworks.com DNS Current — — — —
vendors.evdnetworks.com DNS Current — — — —
video.evdnetworks.com DNS Current — — — —
videos.evdnetworks.com DNS Current — — — —
voip.evdnetworks.com DNS Current — — — —
vpn.evdnetworks.com DNS Current — — — —
vpn1.evdnetworks.com DNS Current — — — —
vpn2.evdnetworks.com DNS Current — — — —
vpn3.evdnetworks.com DNS Current — — — —
vps.evdnetworks.com DNS Current — — — —
waf.evdnetworks.com DNS Current — — — —
wan.evdnetworks.com DNS Current — — — —
warehouse.evdnetworks.com DNS Current — — — —
web.evdnetworks.com DNS Current — — — —
web1.evdnetworks.com DNS Current — — — —
web2.evdnetworks.com DNS Current — — — —
webapi.evdnetworks.com DNS Current — — — —
webapp.evdnetworks.com DNS Current — — — —
webex.evdnetworks.com DNS Current — — — —
webhost.evdnetworks.com DNS Current — — — —
webinar.evdnetworks.com DNS Current — — — —
webinars.evdnetworks.com DNS Current — — — —
webmail.evdnetworks.com DNS Current — — — —
webproxy.evdnetworks.com DNS Current — — — —
webserver.evdnetworks.com DNS Current — — — —
websocket.evdnetworks.com DNS Current — — — —
webtool.evdnetworks.com DNS Current — — — —
webtools.evdnetworks.com DNS Current — — — —
whm.evdnetworks.com DNS Current — — — —
whois.evdnetworks.com DNS Current — — — —
wiki.evdnetworks.com DNS Current — — — —
wordpress.evdnetworks.com DNS Current — — — —
work.evdnetworks.com DNS Current — — — —
worker.evdnetworks.com DNS Current — — — —
worker1.evdnetworks.com DNS Current — — — —
worker2.evdnetworks.com DNS Current — — — —
workspace.evdnetworks.com DNS Current — — — —
wp.evdnetworks.com DNS Current — — — —
ws.evdnetworks.com DNS Current — — — —
www.evdnetworks.com CT Log Current — 3 2026-03-29T15:34:29 Let's Encrypt
www1.evdnetworks.com DNS Current — — — —
www2.evdnetworks.com DNS Current — — — —
www3.evdnetworks.com DNS Current — — — —
xml.evdnetworks.com DNS Current — — — —
zabbix.evdnetworks.com DNS Current — — — —
zoom.evdnetworks.com DNS Current — — — —
Export Recon (CSV)
Δ 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
205.147.88.159
205.147.88.159
AAAA 0 / 0 records
No records
No records
CAA RFC 8659 §4 0 / 0 records
No records
No records
DMARC _dmarc.evdnetworks.com RFC 7489 §6.3 Synchronized 1 / 1 records
v=DMARC1;p=none;rua=mailto:ee5590a40c@rua.easydmarc.us;ruf=mailto:ee5590a40c@ruf.easydmarc.us;fo=1;
v=DMARC1;p=none;rua=mailto:ee5590a40c@rua.easydmarc.us;ruf=mailto:ee5590a40c@ruf.easydmarc.us;fo=1;
MX RFC 5321 Synchronized 1 / 1 records
0 evdnetworks-com.mail.protection.outlook.com.
0 evdnetworks-com.mail.protection.outlook.com.
NS RFC 1035 Synchronized 3 / 3 records
a.ns.interland.net.
a.ns.interland.net.
b.ns.interland.net.
b.ns.interland.net.
c.ns.interland.net.
c.ns.interland.net.
SOA RFC 1035 Synchronized 1 / 1 records
a.ns.interland.net. hostmaster.interland.net. 2024051840 1800 900 864000 2560
a.ns.interland.net. hostmaster.interland.net. 2024051840 1800 900 864000 2560
TXT RFC 7208 §4 Synchronized 1 / 1 records
v=spf1 include:spf.protection.outlook.com -all
v=spf1 include:spf.protection.outlook.com -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.

bb87120cc885ae0eaeb13cbb8dbd43435b37f2adbed3a5b88bce191718f22a9cc85ecf94e74e228ae1df1252e4201a58fe97bdf96a14f26928806da1169545b3
Evaluations reference 12 RFCs. Methods are reproducible using the verification commands provided. Results reflect DNS state at 3 Apr 2026, 06:01 UTC.
Internet Archive — Permanent Record Wayback Machine Can this analysis be independently verified? Archived

This analysis has been automatically submitted to the Internet Archive's Wayback Machine, creating a tamper-evident, third-party-hosted snapshot of the DNS security posture at analysis time. This archived copy is independent of DNS Tool — it provides an independently verifiable record of the analysis at this point in time. Combined with the SHA-3-512 integrity hash, this creates a verifiable chain of evidence for domain security state.

View Archived Snapshot
Snapshot preserved at https://web.archive.org/web/20260403060130/https://dnstool.it-help.tech/analysis/10633/view/E
Download Raw Intelligence Download Checksum (.sha3) Cross-Reference Verification

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

Email Authentication

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

Domain Security

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

Transport Security

Check TLSA record for evdnetworks-com.mail.protection.outlook.com RFC 7672 
dig +noall +answer _25._tcp.evdnetworks-com.mail.protection.outlook.com TLSA
Verify TLS certificate on primary MX (evdnetworks-com.mail.protection.outlook.com) RFC 6698 
openssl s_client -starttls smtp -connect evdnetworks-com.mail.protection.outlook.com:25 -servername evdnetworks-com.mail.protection.outlook.com 2>/dev/null | openssl x509 -noout -subject -dates
Check MTA-STS DNS record RFC 8461 
dig +short _mta-sts.evdnetworks.com TXT
Fetch MTA-STS policy file RFC 8461 
curl -sL https://mta-sts.evdnetworks.com/.well-known/mta-sts.txt
Check TLS-RPT record RFC 8460 
dig +short _smtp._tls.evdnetworks.com TXT

Brand & Trust

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

DNS Records

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

Domain Security

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

Infrastructure Intelligence

RDAP domain registration lookup RFC 9083 
curl -sL 'https://rdap.org/domain/evdnetworks.com' | python3 -m json.tool | head -50

Transport Security

Test STARTTLS on primary MX (evdnetworks-com.mail.protection.outlook.com) RFC 3207 
openssl s_client -starttls smtp -connect evdnetworks-com.mail.protection.outlook.com:25 -servername evdnetworks-com.mail.protection.outlook.com </dev/null 2>/dev/null | head -5

Infrastructure Intelligence

Search Certificate Transparency logs RFC 6962 
curl -s 'https://crt.sh/?q=%25.evdnetworks.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://evdnetworks.com/.well-known/security.txt | head -20

AI Surface

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

Infrastructure Intelligence

ASN lookup for 205.147.88.159 (Team Cymru) 
dig +short 159.88.147.205.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 consistent · 9/9 Evaluated
How confident are these results? Each protocol is independently verified against RFC standards. No self-awarded badges.
SPF
Consistent 15107 runs
DKIM
Consistent 14884 runs
DMARC
Consistent 15088 runs
DANE/TLSA
Consistent 14866 runs
DNSSEC
Consistent 15065 runs
BIMI
Consistent 14881 runs
MTA-STS
Consistent 14902 runs
TLS-RPT
Consistent 14917 runs
CAA
Consistent 14914 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 evdnetworks.com A
Query AAAA records (IPv6) (RFC 1035) 
dig +noall +answer evdnetworks.com AAAA
Query MX records (mail servers) (RFC 1035) 
dig +noall +answer evdnetworks.com MX
Query NS records (nameservers) (RFC 1035) 
dig +noall +answer evdnetworks.com NS
Query TXT records (RFC 1035) 
dig +noall +answer evdnetworks.com TXT

Email Authentication

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

Domain Security

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

Transport Security

Check TLSA record for evdnetworks-com.mail.protection.outlook.com (RFC 7672) 
dig +noall +answer _25._tcp.evdnetworks-com.mail.protection.outlook.com TLSA
Verify TLS certificate on primary MX (evdnetworks-com.mail.protection.outlook.com) (RFC 6698) 
openssl s_client -starttls smtp -connect evdnetworks-com.mail.protection.outlook.com:25 -servername evdnetworks-com.mail.protection.outlook.com 2>/dev/null | openssl x509 -noout -subject -dates
Check MTA-STS DNS record (RFC 8461) 
dig +short _mta-sts.evdnetworks.com TXT
Fetch MTA-STS policy file (RFC 8461) 
curl -sL https://mta-sts.evdnetworks.com/.well-known/mta-sts.txt
Check TLS-RPT record (RFC 8460) 
dig +short _smtp._tls.evdnetworks.com TXT

Brand & Trust

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

DNS Records

Check HTTPS/SVCB records (RFC 9460) 
dig +noall +answer evdnetworks.com HTTPS

Domain Security

Check CDS/CDNSKEY automation records (RFC 7344) 
dig +noall +answer evdnetworks.com CDS

Infrastructure Intelligence

RDAP domain registration lookup (RFC 9083) 
curl -sL 'https://rdap.org/domain/evdnetworks.com' | python3 -m json.tool | head -50

Transport Security

Test STARTTLS on primary MX (evdnetworks-com.mail.protection.outlook.com) (RFC 3207) 
openssl s_client -starttls smtp -connect evdnetworks-com.mail.protection.outlook.com:25 -servername evdnetworks-com.mail.protection.outlook.com </dev/null 2>/dev/null | head -5

Infrastructure Intelligence

Search Certificate Transparency logs (RFC 6962) 
curl -s 'https://crt.sh/?q=%25.evdnetworks.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://evdnetworks.com/.well-known/security.txt | head -20

AI Surface

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

Infrastructure Intelligence

ASN lookup for 205.147.88.159 (Team Cymru) 
dig +short 159.88.147.205.origin.asn.cymru.com TXT

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