Engineer's DNS Intelligence Report
Engineer's DNS Intelligence Report
entegy.rocks
Critical Risk
Engineer workspace · evidence preserved
Read the verdict first. Descend only as far as the incident requires.
This report keeps the complete technical record while separating decision, interpretation, evidence, and raw reproduction into a stable disclosure gradient.
L0PostureL1InterpretationL2EvidenceL3Raw & reproduce
Hurry path
KEYBOARD
!1@2#3$4%5^6
jump to that section
·
esc back to the verdict
DNS Security & Trust Posture
1 protocols configured, 8 not configured
Enterprise DNS Posture: Amazon Route 53 runs enterprise-grade DNS infrastructure — an unsigned DNSSEC chain here reads as a deliberate operator choice, not the gap it would be for a small operator. Network-layer compensating controls are not verifiable via DNS alone; see DNS-layer detail.
Why we go beyond letter grades
What’s Wrong
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)
Publish an SPF record to authorize legitimate mail senders
Publish a DMARC record starting with p=none and rua reporting
DKIM signing inferred from provider — could not directly verify selector
Partial Results:
Some lookups experienced issues:
Dmarc (error)
Sorted by severity — worst first
Email Spoofing
Vulnerable
Brand Impersonation
Not Setup
DNS Tampering
Enterprise
Certificate Control
Open
Monitoring
Not Setup
DANE
Not Deployed
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)
Not Configured
SPF, DMARC, MTA-STS, TLS-RPT, BIMI, DANE, DNSSEC, CAA
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)
Priority Actions
4 total
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.
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.
Medium
Enable DNSSEC
DNSSEC is not enabled for this domain. DNSSEC provides cryptographic authentication of DNS responses, preventing cache poisoning and DNS spoofing attacks.
Registrar (RDAP)
OBSERVED
LIVE
Dreamscape Networks International Pte Ltd
Where domain was purchased
Email Service Provider
Unknown
Unprotected
Web Hosting
Unknown
Where website is hosted
DNS Hosting
Amazon Route 53
Enterprise
Where DNS records are edited
01!1 Identity & policy · L1 Email Security Can this domain be impersonated by email? SPF DMARC DKIM MTA-STS TLS-RPT MX & Routing Vulnerable
Email Security Methodology Can this domain be impersonated by email? Yes no SPF or DMARC protection
SPF Record RFC 7208 §4 Gold
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 Gold
Are spoofed emails rejected or quarantined?
No policy published
Error
No valid DMARC record found
No forensic reporting (ruf) tag — this is correct.
The absence of ruf= is not a gap. RFC 7489 §7.3 warns that forensic reports can expose PII (full message headers or bodies). Google, Microsoft, and Yahoo do not honour ruf= requests regardless. The DMARCbis draft (draft-ietf-dmarc-dmarcbis) has formally removed ruf= from the specification, confirming its deprecation. Omitting ruf= is the recommended modern practice.
RFC 7489 §7.3 — Forensic Reports
RFC 7489 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 Gold
Are outbound emails cryptographically signed?
Not discoverable
Not Discoverable
DKIM not discoverable via common selectors (large providers use rotating selectors)
DKIM key management delegated —
_domainkey.entegy.rocks NS records point to
an external service
(alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com).
DKIM selectors are dynamically managed and may include keys for services beyond what static scanning discovers.
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 Gold
Can attackers downgrade SMTP to intercept mail?
Not prevented
Warning
No valid MTA-STS record found
MTA-STS policy enforcement is evaluated in Mail Transport Security below.
TLS-RPT RFC 8460 §3 Gold
Will failures in TLS delivery be reported?
No reporting
Warning
No valid TLS-RPT record found
02@2 Chain of authority · L1 Domain Security Can DNS answers and certificate issuance be trusted? DANE / TLSA CAA Delegation DNSSEC & NS Open
DANE / TLSA Gold Recon Methodology Can mail servers establish identity without a public CA? No
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).
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).
CAA RFC 8659 §4 Gold Warning
Does this domain restrict who can issue TLS certificates?
No
No CAA records found - any CA can issue certificates
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
| Nameserver | In-Bailiwick | IPv4 Glue | IPv6 Glue | Status |
|---|---|---|---|---|
ns-1171.awsdns-18.org |
No | N/A | N/A | OK |
ns-1618.awsdns-10.co.uk |
No | N/A | N/A | OK |
ns-257.awsdns-32.com |
No | N/A | N/A | OK |
ns-981.awsdns-58.net |
No | N/A | N/A | OK |
NS TTL Comparison Drift
Child TTL: 172800s
Drift: 0s
SOA Serial Consistency Consistent
ns-1171.awsdns-18.org: 1ns-1618.awsdns-10.co.uk: 1ns-257.awsdns-32.com: 1ns-981.awsdns-58.net: 1Domain 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 Gold Unsigned
DNSSEC not configured - DNS responses are unsigned
Alternative Security: Amazon Route 53 provides enterprise-grade DNS with DDoS protection and monitoring.
NS Delegation Verified
4 nameserver(s) configured
Nameservers:
ns-1171.awsdns-18.org
ns-1618.awsdns-10.co.uk
ns-257.awsdns-32.com
ns-981.awsdns-58.net
Managed DNS
All 4 nameservers hosted by Amazon Route 53. Managed DNS provides reliable resolution with provider-maintained infrastructure.
DNS provider(s):
Amazon Route 53
Multi-Resolver Verification
Recon:
Consensus reached -
5 resolvers (Cloudflare, Google, Quad9, OpenDNS, DNS4EU) agree on DNS records
03#3 Delivery path · L1 Transport Security Will mail transport resist downgrade and interception? STARTTLS MTA-STS policy TLS-RPT
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
What Is Measured: Our probe’s TLS 1.3 handshake offers the hybrid post-quantum group
X25519MLKEM768 (X25519 combined with ML-KEM-768). The Key Exchange column reports the group each mail server actually negotiated — direct, observed evidence of its post-quantum readiness toward a hybrid-capable client.Quantum-Safe Hybrid: The session key agreement combines classical X25519 with ML-KEM-768, standardized in FIPS 203 (final, August 2024). This protects the key exchange against “harvest now, decrypt later” collection by a future quantum adversary.
Classical: The server completed the handshake without selecting the offered hybrid group. This is not a deviation — no RFC currently requires post-quantum key exchange. The
X25519MLKEM768 group is defined in draft-ietf-tls-ecdhe-mlkem (Standards Track draft, not yet an RFC); the hybrid approach is described in draft-ietf-tls-hybrid-design (IESG-approved Informational). Servers supporting only other hybrid groups also read as Classical here.Transition Outlook: NIST’s draft transition guidance (NIST IR 8547) projects quantum-vulnerable algorithms being deprecated after 2030 and disallowed after 2035. Hybrid key exchange requires TLS 1.3. This finding is informational and does not affect this domain’s grade.
04$4 Human-visible identity · L1 Brand & Trust Can this brand be convincingly faked? BIMI & VMC CAA · see Domain Security Not Setup
05%5 Ownership & attack surface · L1 Infrastructure Intelligence Who operates this domain, and what is exposed? Registrar / RDAP security.txt AI Surface Subdomains
Vulnerability Disclosure Policy (security.txt) Is there a verified way to report security issues? No RFC 9116
Could not fetch security.txt
Fetch error: Connection failed
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.
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 ns-981.awsdns-58.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: ns-981.awsdns-58.net, ns-1618.awsdns-10.co.uk, ns-257.awsdns-32.com, ns-1171.awsdns-18.org
Nameserver Fleet Matrix Healthy
Analyzed 4 nameserver(s) for entegy.rocks — Per-nameserver reachability, ASN diversity, SOA serial sync, and lame delegation checks.
| Nameserver | IPv4 | IPv6 | ASN / Operator | UDP | TCP | AA | SOA Serial | Anycast Node |
|---|---|---|---|---|---|---|---|---|
ns-1171.awsdns-18.org |
205.251.196.147 | 2600:9000:5304:9300::1 |
AS16509
Amazon.com, Inc. |
1 | N/A | |||
ns-981.awsdns-58.net |
205.251.195.213 | 2600:9000:5303:d500::1 |
AS16509
Amazon.com, Inc. |
1 | N/A | |||
ns-257.awsdns-32.com |
205.251.193.1 | 2600:9000:5301:100::1 |
AS16509
Amazon.com, Inc. |
1 | N/A | |||
ns-1618.awsdns-10.co.uk |
205.251.198.82 | 2600:9000:5306:5200::1 |
AS16509
Amazon.com, Inc. |
1 | N/A |
Unique ASNs
1
Unique Operators
1
Unique /24 Prefixes
4
Diversity Score
Fair
1 ASN(s), 4 /24 prefix(es) — consider adding diversity
Infrastructure Intelligence Who hosts this domain and what services power it? Direct
ASN / Network Info
No IP addresses to look up
Edge / CDN Success
Domain appears to use direct origin hosting
SaaS TXT Footprint Success 1 service
Detected 1 SaaS verification record
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.
| Service | Verification Record |
|---|---|
google-site-verification=3cxwoA4xrocnfHAspXZ8mvv2S7Eo35nFo534BIIQ0mY |
Traffic & Routing Where does this domain's traffic actually terminate?
AIPv4 Address
No A records
Domain may use AAAA (IPv6) only or CNAME
AAAAIPv6 Address
No AAAA records
IPv6 not configured
MXMail Servers
No MX records
Domain cannot receive email
SRVServices
_caldavs._tcp: alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com.
_imaps._tcp: alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com.
_submission._tcp: alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com.
_xmpp-client._tcp: alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com.
_sip._tls: alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com.
_sipfederationtls._tcp: alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com.
_carddavs._tcp: alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com.
_autodiscover._tcp: alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com.
SIP, XMPP, or other service endpoints
Web:
No direct IP
Mail:
Not configured
Services:
8 endpoints
Subdomain Discovery RFC 6962 Recon LIVE What subdomains and infrastructure are exposed in certificate logs? 529 subdomains discovered
How did we find these?
28 unique certificates
529 current
0 expired
500 CNAMEs
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:
*.entegy.rocks
Active
4 certs
1 CA: Amazon
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
(2 CAs observed across CT log history)
| Certificate Authority | Certs | First Issued | Last Issued | Status |
|---|---|---|---|---|
Amazon |
19 | 2025-07-18 | 2026-06-25 | Active |
Let's Encrypt |
9 | 2026-05-24 | 2026-07-28 | Active |
| Subdomain | Source | Status | Provider / CNAME | Certificates | First Seen | Issuer(s) |
|---|---|---|---|---|---|---|
a.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
academy.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
account.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
accounting.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
accounts.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
ad.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
adfs.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
admin.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
admin1.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
admin2.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
alert.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
alerts.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
alextest3.entegy.rocks
|
CT Log | Current | — | 2 | 2026-05-25T23:02:24 | Let's Encrypt |
alpha.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
analytics.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
ap-south.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
ap.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
apac.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
api-us.entegy.rocks
|
CT Log | Current | — | 2 | 2025-10-29T00:00:00 | Amazon |
api.entegy.rocks
|
DNS | Current |
entegy-devapi.elasticbeanstalk.com
|
4 | 2025-07-21 | Amazon |
api1.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
api2.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
api3.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
apigw.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
apis.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
apiv3.au.entegy.rocks
|
CT Log | Current | — | 2 | 2026-03-24T00:00:00 | Amazon |
apiv3.us.entegy.rocks
|
CT Log | Current | — | 1 | 2025-12-01T00:00:00 | Amazon |
apm.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
app.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
app1.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
app2.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
appointments.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
apps.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
archive.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
archives.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
asia.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
assets.entegy.rocks
|
CT Log | Current | — | 2 | 2025-11-09T00:00:00 | Amazon |
atom.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
au.cms.entegy.rocks
|
CT Log | Current | — | — | — | — |
au.entegy.rocks
|
CT Log | Current | — | 4 | 2026-07-28T23:02:47 | Let's Encrypt |
au.registration.entegy.rocks
|
CT Log | Current | — | 4 | 2026-07-28T23:06:38 | Let's Encrypt |
auth.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
auth0.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
autoconfig.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
autodiscover.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
b.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
backup.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
backup1.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
backup2.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
beta.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
bi.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
bigdata.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
billing.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
bitbucket.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
blob.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
blog.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
booking.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
broker.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
bucket.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
build.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
builds.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
c.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
ca.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
cache.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
cal.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
calendar.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
campaigns.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
careers.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
cart.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
catalog.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
cd.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
cdn.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
cdn1.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
cdn2.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
cdn3.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
cert.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
certs.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
chat.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
checkout.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
ci.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
client.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
clients.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
cloud.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
cms.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
cname.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
code.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
community.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
compliance.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
conference.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
config.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
configuration.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
confluence.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
connect.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
console.entegy.rocks
|
DNS | Current | — | 4 | 2025-07-21 | Amazon |
containers.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
content.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
corecontainer.entegy.rocks
|
CT Log | Current | — | 2 | 2026-06-18T00:00:00 | Amazon |
corp.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
corporate.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
courses.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
cpanel.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
crl.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
crm.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
d.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
dashboard.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
data.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
data1.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
data2.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
database.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
datadog.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
db.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
db1.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
db2.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
dedicated.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
demo.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
deploy.entegy.rocks
|
DNS | Current | — | 4 | 2025-07-21 | Amazon |
deployment.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
dev.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
dev1.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
dev2.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
develop.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
developer.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
developers.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
devices.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
devops.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
directory.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
discuss.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
discussions.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
dns.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
dns1.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
dns2.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
dnscheck.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
dnstool.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
doc.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
docker.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
docs.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
documentation.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
download.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
downloads.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
drupal.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
e.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
ecommerce.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
edge.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
edge1.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
edge2.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
education.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
elastic.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
elasticsearch.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
email.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
emea.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
endpoint.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
erp.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
es.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
etl.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
eu-west.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
eu.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
event.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
events.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
exchange.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
ext.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
f.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
faq.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
feed.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
feedback.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
feeds.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
file.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
files.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
finance.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
firewall.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
forms.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
forum.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
forums.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
ftp.entegy.rocks
|
DNS | Current | — | 4 | 2025-07-21 | Amazon |
ftp1.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
ftp2.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
fw.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
gateway.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
geo.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
gis.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
git.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
github.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
gitlab.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
go.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
grafana.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
graphql.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
gw.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
gw1.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
gw2.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
haproxy.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
health.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
healthcheck.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
help.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
helpdesk.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
hiring.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
host.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
hosting.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
hq.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
hr.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
hris.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
hub.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
id.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
identity.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
image.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
images.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
imap.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
img.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
int.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
internal.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
intranet.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
inventory.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
investor.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
investors.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
invoice.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
ir.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
it.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
itsm.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
itsupport.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
jenkins.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
jira.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
jobs.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
k8s.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
kafka.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
kb.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
kibana.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
kong.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
kubernetes.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
lab.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
labs.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
lan.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
lb.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
ldap.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
learn.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
learning.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
legal.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
link.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
links.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
live.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
lms.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
loadbalancer.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
location.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
log.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
login.entegy.rocks
|
DNS | Current |
us.cms.entegy.rocks
|
4 | 2025-07-21 | Amazon |
logs.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
lookup.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
m.entegy.rocks
|
DNS | Current | — | 4 | 2025-07-21 | Amazon |
mail.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
mail1.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
mail2.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
mail3.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
mailgw.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
mailhost.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
mailrelay.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
mailserver.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
manage.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
management.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
manager.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
map.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
maps.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
marketing.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
mdm.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
media.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
meet.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
meeting.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
memcached.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
metrics.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
microservices.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
mobile.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
mongo.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
mongodb.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
monitor.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
monitoring.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
mq.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
mta.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
mx.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
mx1.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
mx2.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
mx3.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
mx4.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
mx5.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
mxtoolbox.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
my.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
myaccount.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
mysql.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
na.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
nagios.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
net.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
netadmin.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
nettool.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
nettools.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
network.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
news.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
nginx.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
nicks-website.entegy.rocks
|
CT Log | Current | — | — | — | — |
node1.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
node2.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
node3.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
notifications.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
notify.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
ns.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
ns1.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
ns2.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
ns3.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
ns4.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
ns5.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
ns6.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
o365.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
oauth.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
object.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
ocsp.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
office.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
okta.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
order.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
orders.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
origin.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
origin1.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
origin2.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
outlook.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
owa.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
panel.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
partner.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
partners.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
pay.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
payment.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
payments.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
payroll.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
pbx.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
phone.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
photos.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
pingdom.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
pki.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
plesk.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
policies.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
policy.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
pop.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
pop3.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
portal.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
portal2.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
postgres.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
pre.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
preprod.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
press.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
preview.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
primary.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
print.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
printer.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
privacy.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
private.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
product.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
products.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
profile.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
prometheus.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
promo.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
proxy-test.entegy.rocks
|
CT Log | Current | — | — | — | — |
proxy.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
proxy1.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
proxy2.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
public.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
qa.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
queue.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
r.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
ra.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
rabbitmq.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
rancher.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
realtime.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
recruit.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
redirect.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
redis.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
register.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
registration-us.entegy.rocks
|
CT Log | Current | — | — | — | — |
registration.entegy.rocks
|
CT Log | Current | — | — | — | — |
registry.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
relay.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
relay1.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
releases.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
remote.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
repo.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
report.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
reporting.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
reports.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
repos.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
reservations.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
resources.entegy.rocks
|
CT Log | Current | — | 2 | 2026-05-03T00:00:00 | Amazon |
rest.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
rss.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
rt.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
s3.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
sandbox.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
sandbox1.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
sandbox2.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
scan.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
scanner.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
schedule.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
scp.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
search.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
secondary.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
secrets.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
secure.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
server.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
server1.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
server2.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
server3.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
service.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
servicedesk.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
services.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
sftp.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
share.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
shop.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
signin.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
signup.entegy.rocks
|
DNS | Current |
d120zo2b6rdq5t.cloudfront.net
|
4 | 2025-07-21 | Amazon |
sip.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
slack.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
smtp.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
smtp1.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
smtp2.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
socket.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
solr.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
speedtest.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
sql.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
srv.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
srv1.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
srv2.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
ssh.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
ssl.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
sso.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
stage.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
staging.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
static.entegy.rocks
|
CT Log | Current | — | 1 | 2025-09-08T00:00:00 | Amazon |
static1.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
static2.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
statistics.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
stats.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
status.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
statuspage.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
stg.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
storage.entegy.rocks
|
CT Log | Current | — | 1 | 2025-09-02T00:00:00 | Amazon |
store.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
stream.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
streaming.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
support.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
support2.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
survey.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
surveys.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
svc.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
svn.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
swift.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
sysadmin.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
syslog.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
talent.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
teams.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
techsupport.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
tel.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
telecom.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
terms.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
test.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
test1.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
test2.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
testing.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
testreg.entegy.rocks
|
CT Log | Current | — | 4 | 2026-07-28T23:08:57 | Let's Encrypt |
ticket.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
tickets.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
tls.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
tool.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
tools.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
trace.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
tracing.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
tracking.entegy.rocks
|
DNS | Current | — | 4 | 2025-07-21 | Amazon |
training.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
uat.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
upload.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
uploads.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
uptime.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
url.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
us-east.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
us-west.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
us.cms.entegy.rocks
|
CT Log | Current | — | — | — | — |
us.entegy.rocks
|
DNS | Current | — | 4 | 2025-07-21 | Amazon |
us.registration.entegy.rocks
|
CT Log | Current | — | 4 | 2026-07-28T23:16:11 | Let's Encrypt |
utility.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
varnish.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
vault.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
vendor.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
vendors.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
video.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
videos.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
voip.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
vpn.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
vpn1.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
vpn2.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
vpn3.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
vps.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
waf.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
wan.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
warehouse.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
web.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
web1.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
web2.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
webapi.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
webapp.entegy.rocks
|
DNS | Current | — | 4 | 2025-07-21 | Amazon |
webappau.entegy.rocks
|
CT Log | Current | — | 6 | 2025-07-21T00:00:00 | Amazon |
webappus.entegy.rocks
|
CT Log | Current | — | 4 | 2026-06-25T00:00:00 | Amazon |
webex.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
webhost.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
webinar.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
webinars.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
webmail.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
webproxy.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
webserver.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
websocket.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
webtool.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
webtools.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
whm.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
whois.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
wiki.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
wordpress.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
work.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
worker.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
worker1.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
worker2.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
workspace.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
wp.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
ws.apiv3.au.entegy.rocks
|
CT Log | Current | — | 4 | 2026-06-22T00:00:00 | Amazon |
ws.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
www.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
www1.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
www2.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
www3.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
xml.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
zabbix.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
zoom.entegy.rocks
|
DNS | Current |
alb-entegy-legacy-80206160.ap-southeast-2.elb.amazonaws.com
|
4 | 2025-07-21 | Amazon |
Δ No Propagation Issues:
All DNS records are synchronized between resolver and authoritative nameserver.
06^6 Raw records & reproducibility · L2–L3 Evidence & Verification Can another engineer reproduce every material claim? Analysis Confidence Intelligence Currency What changed Raw record diff Integrity seal Reproduce
Resolver agreement is inconsistent for some protocols, limiting confidence. Data currency and system maturity are adequate.
Accuracy 60%
Currency 71/100
Maturity gold
Limiting factor: Resolver agreement is low for this scan — some protocols returned inconsistent results across resolvers
Currentness Excellent
TTL Compliance Excellent
Completeness Stale
Source Credibility Excellent
TTL Relevance Degraded
ICuAE Details
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 |
|---|---|---|---|---|
| SOA | 15 minutes (900s) |
1 hour (3600s) |
medium | SOA TTL is below typical — observed 15 minutes (900s), 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 | 5 minutes (300s) |
1 hour (3600s) |
high | TXT TTL is below typical — observed 5 minutes (300s), 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.
Primary NS
ns-1618.awsdns-10.co.uk
Serial
1
Admin
awsdns-hostmaster.amazon.com
Provider
AWS Route 53
| Timer | Value | RFC 1912 Range |
|---|---|---|
| Refresh | 7200s | 1,200–43,200s (20 min – 12 hrs) |
| Retry | 900s | Fraction of Refresh |
| Expire | 1209600s | 1,209,600–2,419,200s (14–28 days) |
| Minimum (Neg. Cache) | 86400s | 300–86,400s (5 min – 1 day) |
All SOA timer values are within RFC 1912 recommended ranges.
Independent RFC compliance assessment for AWS Route 53. Each finding cites the specific RFC section and reports what the engineering community consensus is. We report honestly — if a provider deviates from standards, we explain what they did differently and what the RFCs actually say.
Alias record TTLs fixed at 60s
RFC 1035 §3.2.1
AWS Route 53 alias records pointing to AWS resources (ELB, CloudFront, S3, API Gateway) have a fixed TTL of 60 seconds that cannot be modified. Route 53 alias records are an AWS-specific extension — not part of standard DNS RFCs. They solve the CNAME-at-apex problem (RFC prohibits CNAME at zone apex) by appearing as A/AAAA records to resolvers. The 60-second TTL ensures fast failover but removes administrator TTL control.
Proprietary extension — not covered by DNS RFCs
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
0 / 0 records
No records
No records
AAAA
0 / 0 records
No records
No records
No records
No records
No records
No records
ns-1171.awsdns-18.org.
ns-1171.awsdns-18.org.
ns-1618.awsdns-10.co.uk.
ns-1618.awsdns-10.co.uk.
ns-257.awsdns-32.com.
ns-257.awsdns-32.com.
ns-981.awsdns-58.net.
ns-981.awsdns-58.net.
ns-1618.awsdns-10.co.uk. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400
ns-1618.awsdns-10.co.uk. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400
google-site-verification=3cxwoA4xrocnfHAspXZ8mvv2S7Eo35nFo534BIIQ0mY
google-site-verification=3cxwoA4xrocnfHAspXZ8mvv2S7Eo35nFo534BIIQ0mY
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?
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.
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.
1a82e280558c50259318d07b2cbf2b1d4e48deae59e5bb97dcac144eadaba815b423f04281b5c53c5c769f4a1950e29b40c31ce327a615c805eebda0f26ad628
Evaluations reference 12 RFCs. Methods are reproducible using the verification commands provided. Results reflect DNS state at 29 Jul 2026, 03:47 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.
Snapshot preserved at
https://web.archive.org/web/20260729034729/https://dnstool.it-help.tech/analysis/18103/view/E
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-entegy.rocks.json.sha3 && echo '---' && openssl dgst -sha3-512 dns-intelligence-entegy.rocks.json
Python 3 (cross-platform)
python3 -c "import hashlib; print(hashlib.sha3_512(open('dns-intelligence-entegy.rocks.json','rb').read()).hexdigest())"
sha3sum (coreutils 9+)
sha3sum -a 512 dns-intelligence-entegy.rocks.json
Compare the output against the
.sha3 file or the checksum API at /api/analysis/18103/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 entegy.rocks. 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 entegy.rocks A
Query AAAA records (IPv6) RFC 1035
dig +noall +answer entegy.rocks AAAA
Query MX records (mail servers) RFC 1035
dig +noall +answer entegy.rocks MX
Query NS records (nameservers) RFC 1035
dig +noall +answer entegy.rocks NS
Query TXT records RFC 1035
dig +noall +answer entegy.rocks TXTEmail Authentication
Check SPF record RFC 7208
dig +short entegy.rocks TXT | grep -i spf
Check DMARC policy RFC 7489
dig +short _dmarc.entegy.rocks TXT
Check DKIM key for selector 'default' RFC 6376
dig +short default._domainkey.entegy.rocks TXT
Check DKIM key for selector 'google' RFC 6376
dig +short google._domainkey.entegy.rocks TXT
Check DKIM key for selector 'selector1' RFC 6376
dig +short selector1._domainkey.entegy.rocks TXT
Check DKIM key for selector 'selector2' RFC 6376
dig +short selector2._domainkey.entegy.rocks TXTDomain Security
Check DNSSEC DNSKEY records RFC 4035
dig +dnssec +noall +answer entegy.rocks DNSKEY
Check DNSSEC DS records RFC 4035
dig +noall +answer entegy.rocks DS
Validate DNSSEC chain (requires DNSSEC-validating resolver) RFC 4035
dig +dnssec +cd entegy.rocks A @1.1.1.1Transport 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.entegy.rocks TXT
Fetch MTA-STS policy file RFC 8461
curl -sL https://mta-sts.entegy.rocks/.well-known/mta-sts.txt
Check TLS-RPT record RFC 8460
dig +short _smtp._tls.entegy.rocks TXTBrand & Trust
Check BIMI record BIMI Draft
dig +short default._bimi.entegy.rocks TXT
Check CAA records (certificate authority authorization) RFC 8659
dig +noall +answer entegy.rocks CAADNS Records
Check HTTPS/SVCB records RFC 9460
dig +noall +answer entegy.rocks HTTPSDomain Security
Check CDS/CDNSKEY automation records RFC 7344
dig +noall +answer entegy.rocks CDSInfrastructure Intelligence
RDAP domain registration lookup RFC 9083
curl -sL 'https://rdap.org/domain/entegy.rocks' | python3 -m json.tool | head -50
Search Certificate Transparency logs RFC 6962
curl -s 'https://crt.sh/?q=%25.entegy.rocks&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://entegy.rocks/.well-known/security.txt | head -20AI Surface
Check for llms.txt
curl -sI https://entegy.rocks/llms.txt | head -5
Check robots.txt for AI crawler rules
curl -s https://entegy.rocks/robots.txt | grep -i -E 'GPTBot|ChatGPT|Claude|Anthropic|Google-Extended|CCBot|PerplexityBot'
Commands use
dig, openssl, and curl — standard tools available on macOS, Linux, and WSL. Results may vary slightly due to DNS propagation timing and resolver caching.
Intelligence Confidence Audit Engine
gold · 9/9 Evaluated
How confident are these results? Each protocol is independently verified against RFC standards. No self-awarded badges.
SPF
Gold
15673 runs
DKIM
Gold
15463 runs
DMARC
Gold
15654 runs
DANE/TLSA
Gold
15445 runs
DNSSEC
Gold
15632 runs
BIMI
Gold
15460 runs
MTA-STS
Gold
15481 runs
TLS-RPT
Gold
15496 runs
CAA
Gold
15493 runs
Maturity:
Development
→
Verified
→
Consistent
→
Gold
→
Gold Master
Appendix: Verification Commands
DNS Records
dig +noall +answer entegy.rocks Adig +noall +answer entegy.rocks AAAAdig +noall +answer entegy.rocks MXdig +noall +answer entegy.rocks NSdig +noall +answer entegy.rocks TXTEmail Authentication
dig +short entegy.rocks TXT | grep -i spfdig +short _dmarc.entegy.rocks TXTdig +short default._domainkey.entegy.rocks TXTdig +short google._domainkey.entegy.rocks TXTdig +short selector1._domainkey.entegy.rocks TXTdig +short selector2._domainkey.entegy.rocks TXTDomain Security
dig +dnssec +noall +answer entegy.rocks DNSKEYdig +noall +answer entegy.rocks DSdig +dnssec +cd entegy.rocks A @1.1.1.1Transport Security
dig +noall +answer _25._tcp.MX_HOST TLSAdig +short _mta-sts.entegy.rocks TXTcurl -sL https://mta-sts.entegy.rocks/.well-known/mta-sts.txtdig +short _smtp._tls.entegy.rocks TXTBrand & Trust
dig +short default._bimi.entegy.rocks TXTdig +noall +answer entegy.rocks CAADNS Records
dig +noall +answer entegy.rocks HTTPSDomain Security
dig +noall +answer entegy.rocks CDSInfrastructure Intelligence
curl -sL 'https://rdap.org/domain/entegy.rocks' | python3 -m json.tool | head -50curl -s 'https://crt.sh/?q=%25.entegy.rocks&output=json' | python3 -c "import json,sys; [print(e['name_value']) for e in json.load(sys.stdin)]" | sort -u | head -20curl -sL https://entegy.rocks/.well-known/security.txt | head -20AI Surface
curl -sI https://entegy.rocks/llms.txt | head -5curl -s https://entegy.rocks/robots.txt | grep -i -E 'GPTBot|ChatGPT|Claude|Anthropic|Google-Extended|CCBot|PerplexityBot'