Engineer's DNS Intelligence Report
Engineer's DNS Intelligence Report
okplay.ph
Medium 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
4 protocols configured, 5 not configured
DMARC is published at p=none with aggregate reporting enabled (RFC 7489 §6.3) — authentication results are reported but no enforcement is requested. The domain separately deploys CAA and an SPF -all hard fail, so an unfinished rollout is the less likely reading. It's possible this organization is deliberately prioritising observation over enforcement. What this means if you receive mail from this domain: p=none blocks nothing — a spoofed message that fails authentication is delivered to the inbox exactly as it would be with no DMARC record at all. Moving to quarantine or reject adds protection while aggregate reporting continues unchanged.
Enterprise DNS Posture: Cloudflare 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
Sorted by severity — worst first
Email Spoofing
Partial
Brand Impersonation
Not Setup
DNS Tampering
Enterprise
Certificate Control
Configured
Monitoring
Partial
DANE
Not Deployed
Not Configured
MTA-STS, TLS-RPT, BIMI, DANE, DNSSEC
Recommended
Move DMARC policy from 'none' to 'quarantine' or 'reject'
Monitoring
DMARC record has configuration warnings — review recommended, DKIM signing inferred from provider — could not directly verify selector
Configured
SPF (hard fail), DMARC (with warnings), DKIM (inferred via Unknown), CAA
Priority Actions
4 total
Achievable posture: Low Risk
High
Upgrade DMARC from p=none
Your DMARC policy is monitor-only (p=none). Upgrade to p=quarantine or p=reject after reviewing reports to actively prevent spoofing.
Medium
Enable DNSSEC
DNSSEC is not enabled for this domain. DNSSEC provides cryptographic authentication of DNS responses, preventing cache poisoning and DNS spoofing attacks.
Low
Add TLS-RPT Reporting
TLS-RPT (TLS Reporting) sends you reports about TLS connection failures when other servers try to deliver mail to your domain.
Registrar (NS INFERENCE)
INFERRED
LIVE
Cloudflare Registrar
Inferred from NS records
Email Service Provider
Unknown
Moderately Protected
Web Hosting
INFERRED
Cloudflare (CDN)
Where website is hosted
DNS Hosting
Cloudflare
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 Partial
Email Security Methodology Can this domain be impersonated by email? Yes DMARC requests no enforcement (p=none)
SPF Record RFC 7208 §4 Gold
Does this domain declare who may send email on its behalf?
Yes
Success
-all
1/10 lookups
SPF valid with strict enforcement (-all), 1/10 lookups
v=spf1 +include:spf.onlarksuite.com -all
RFC 7489: -all may cause rejection before DMARC evaluation, preventing DKIM from being checked
RFC 7208 Conformant — This SPF record conforms to the syntax and semantics defined in RFC 7208 §4.
RFC Failure Mode: Unlike DMARC (where unknown tags are silently ignored per RFC 7489 §6.3), SPF with unrecognized mechanisms produces a PermError per RFC 7208 §4.6 — the record fails loudly rather than silently.
Related CVEs:
CVE-2024-7208 (multi-tenant domain spoofing),
CVE-2024-7209 (shared SPF exploitation),
CVE-2023-51764 (SMTP smuggling bypasses SPF)
SPF hard fail (-all): compliance-strong, but can short-circuit DMARC.
RFC 7489 notes that -all can cause some receivers to reject mail during the SMTP transaction — before DKIM is checked and before DMARC can evaluate the result. A message that would pass DMARC via DKIM alignment may be rejected prematurely. For most domains, ~all + DMARC p=reject is the strongest compatible posture — it allows every authentication method (SPF, DKIM, DMARC) to be fully evaluated before a decision is made.
DMARC is monitoring only (p=none). -all provides some SPF-level protection, but DMARC isn't enforcing. Adding p=reject and considering ~all for compatibility would be far more effective.
DMARC is monitoring only (p=none). -all provides some SPF-level protection, but DMARC isn't enforcing. Adding p=reject and considering ~all for compatibility would be far more effective.
DMARC Policy RFC 7489 §6.3 Gold
Are spoofed emails rejected or quarantined?
Monitoring only
Warning
p=none
DMARC in monitoring mode (p=none) - spoofed mail still delivered, no enforcement
v=DMARC1; p=none; rua=mailto:dmarc-reports@okplay.ph;
Policy p=none provides no protection - spoofed emails reach inboxes
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
Advanced cryptographic posture detected.
DMARC is published at p=none with aggregate reporting enabled (RFC 7489 §6.3) — authentication results are reported but no enforcement is requested. The domain separately deploys CAA and an SPF -all hard fail, so an unfinished rollout is the less likely reading. It's possible this organization is deliberately prioritising observation over enforcement. What this means if you receive mail from this domain: p=none blocks nothing — a spoofed message that fails authentication is delivered to the inbox exactly as it would be with no DMARC record at all. Moving to quarantine or reject adds protection while aggregate reporting continues unchanged.
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.okplay.ph NS records point to
an external service
(3c74tnj6sru9.okplay.ph.eo.dnse5.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 Enterprise
DANE / TLSA Gold Recon Methodology Can mail servers establish identity without a public CA? No
No DANE/TLSA records found (checked 3 MX hosts)
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 Success
Does this domain restrict who can issue TLS certificates?
Yes
CAA configured - only DigiCert, Let's Encrypt, cansignhttpexchanges=yes, ssl.com, Sectigo can issue certificates (wildcard issuance: Let's Encrypt, cansignhttpexchanges=yes, ssl.com, Sectigo, DigiCert per RFC 8659 §4.3)
Authorized CAs:
DigiCert
Let's Encrypt
cansignhttpexchanges=yes
ssl.com
Sectigo
0 issue "comodoca.com"
0 issue "digicert.com; cansignhttpexchanges=yes"
0 issue "letsencrypt.org"
0 issue "pki.goog; cansignhttpexchanges=yes"
0 issue "sectigo.com"
0 issue "ssl.com"
0 issuewild "comodoca.com"
0 issuewild "digicert.com; cansignhttpexchanges=yes"
0 issuewild "letsencrypt.org"
0 issuewild "pki.goog; cansignhttpexchanges=yes"
0 issuewild "ssl.com"
Since September 2025, all public CAs must verify domain control from multiple geographic locations (Multi-Perspective Issuance Corroboration, CA/B Forum Ballot SC-067). CAA records are now checked from multiple network perspectives before certificate issuance.
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 |
|---|---|---|---|---|
collins.ns.cloudflare.com |
No | N/A | N/A | OK |
dane.ns.cloudflare.com |
No | N/A | N/A | OK |
NS TTL Comparison Drift
Child TTL: 86400s
Drift: 0s
SOA Serial Consistency Consistent
collins.ns.cloudflare.com: 2.41140234e+09dane.ns.cloudflare.com: 2.41140234e+09Domain 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: Cloudflare provides enterprise-grade DNS with DDoS protection and monitoring.
CAA records configured
NS Delegation Verified
2 nameserver(s) configured
Nameservers:
collins.ns.cloudflare.com
dane.ns.cloudflare.com
Managed DNS
All 2 nameservers hosted by Cloudflare. Managed DNS provides reliable resolution with provider-maintained infrastructure.
DNS provider(s):
Cloudflare
Multi-Resolver Verification
Recon:
Consensus reached -
5 resolvers (Cloudflare, Google, Quad9, OpenDNS, DNS4EU) agree on DNS records
HTTPS / SVCB Records RFC 9460 Success HTTPS
HTTPS records found
| Priority | Target | ALPN | ECH | Raw |
|---|---|---|---|---|
| 1 | . |
h2 | No | okplay.ph. 300 IN HTTPS 1 . alpn="h2" ipv4hint="104.18.30.191,104.18.31.191" |
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 transport encryption policy detected — mail delivery relies on opportunistic TLS
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 — Remote probe failed (HTTP 502) and local port 25 is blocked. Transport security is assessed via DNS policy records per NIST SP 800-177 Rev. 1.
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
No security.txt found
A security.txt file at
/.well-known/security.txt provides security researchers with a standardized way to report vulnerabilities.
See securitytxt.org for a generator.
AI Surface Scanner Beta Is this domain discoverable by AI — and protected from abuse? No
No significant AI surface findings
llms.txt llmstxt.org
Is this domain publishing AI-readable brand context?
No
No llms.txt found
No llms-full.txt found
AI Crawler Governance (robots.txt) RFC 9309 IETF Draft
Are AI crawlers explicitly allowed or blocked?
No directives
No robots.txt found
Content-Usage Directive IETF Draft
Does the site express AI content-usage preferences?
Not Configured
No Content-Usage directive detected.
The IETF AI Preferences working group is developing a
Content-Usage: directive for robots.txt that lets site owners declare whether their content may be used for AI training and inference. This is an active draft, not yet a ratified standard.
Example: Add
Content-Usage: ai=no to robots.txt to deny AI training, or Content-Usage: ai=allow to explicitly permit it.
Without this directive, AI crawler behavior depends on individual crawler policies and User-agent rules.
AI Recommendation Poisoning
Is this site trying to manipulate AI recommendations?
No
No AI recommendation poisoning indicators found
Hidden Prompt Artifacts
Is hidden prompt-injection text present in the source?
No
No hidden prompt-like artifacts detected
Public Exposure Checks Are sensitive files or secrets exposed? No
No exposed secrets detected in public page source — same-origin, non-intrusive scan of publicly visible page source and scripts.
No exposed secrets, API keys, or credentials were detected in publicly accessible page source or scripts.
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 Not Checked
Nmap not available — 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 | Not tested |
| Open Recursion | Disabled | Not tested |
| Nameserver Identity | Hidden | Not tested |
| Cache Snooping | Protected | Not tested |
Nameserver Fleet Matrix Healthy
Analyzed 2 nameserver(s) for okplay.ph — Per-nameserver reachability, ASN diversity, SOA serial sync, and lame delegation checks.
| Nameserver | IPv4 | IPv6 | ASN / Operator | UDP | TCP | AA | SOA Serial | Anycast Node |
|---|---|---|---|---|---|---|---|---|
collins.ns.cloudflare.com |
172.64.34.226 108.162.194.226 162.159.38.226 |
2803:f800:50::6ca2:c2e2 2a06:98c1:50::ac40:22e2 2606:4700:50::a29f:26e2 |
AS13335
Cloudflare, Inc. |
2411402340 | N/A | |||
dane.ns.cloudflare.com |
172.64.33.97 108.162.193.97 173.245.59.97 |
2606:4700:58::adf5:3b61 2803:f800:50::6ca2:c161 2a06:98c1:50::ac40:2161 |
AS13335
Cloudflare, Inc. |
2411402340 | N/A |
Unique ASNs
1
Unique Operators
1
Unique /24 Prefixes
6
Diversity Score
Fair
1 ASN(s), 6 /24 prefix(es) — consider adding diversity
Infrastructure Intelligence Who hosts this domain and what services power it? Direct
ASN / Network Success
Resolved 1 unique ASN(s) across 2 IP address(es)
| ASN | Name | Country |
|---|---|---|
AS13335 |
Cloudflare, Inc. | US |
IPv4 Mappings:
104.18.30.191 → AS13335 (104.18.16.0/20)104.18.31.191 → AS13335 (104.18.16.0/20)Edge / CDN Success Cloudflare
Domain is served through Cloudflare
Behind CDN
Origin Hidden
ASN 13335 is Cloudflare
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=DserNiDUrQIE9wG4H8cX7txvn147b5Ng0TZCTYLBsQQ |
Traffic & Routing Where does this domain's traffic actually terminate?
AIPv4 Address
104.18.30.191
104.18.31.191
Where the domain points for web traffic
AAAAIPv6 Address
No AAAA records
IPv6 not configured
MXMail Servers
1 mx1.larksuite.com.
10 mx3.larksuite.com.
5 mx2.larksuite.com.
Priority + mail server for email delivery
SRVServices
_caldavs._tcp: 3c74tnj6sru9.okplay.ph.eo.dnse5.com.
_imaps._tcp: 3c74tnj6sru9.okplay.ph.eo.dnse5.com.
_carddavs._tcp: 3c74tnj6sru9.okplay.ph.eo.dnse5.com.
_submission._tcp: 3c74tnj6sru9.okplay.ph.eo.dnse5.com.
_autodiscover._tcp: 3c74tnj6sru9.okplay.ph.eo.dnse5.com.
_sip._tls: 3c74tnj6sru9.okplay.ph.eo.dnse5.com.
_sipfederationtls._tcp: 3c74tnj6sru9.okplay.ph.eo.dnse5.com.
_xmpp-client._tcp: 3c74tnj6sru9.okplay.ph.eo.dnse5.com.
SIP, XMPP, or other service endpoints
Web:
Reachable
(2 IPv4, 0 IPv6)
Mail:
3 servers
Services:
8 endpoints
Subdomain Discovery RFC 6962 Recon LIVE What subdomains and infrastructure are exposed in certificate logs? 511 subdomains discovered
How did we find these?
Certificate Transparency Logs Unavailable
The results below are from DNS probing only and may be significantly incomplete. CT logs typically reveal hundreds or thousands of additional subdomains via certificate issuance history (RFC 6962). The CT log server was temporarily unavailable and is in a cooldown period.
CT logs unavailable
511 current
0 expired
509 CNAMEs
Source: Certificate Transparency + DNS Intelligence
Subdomains discovered via CT logs (RFC 6962), DNS probing of common service names, and CNAME chain traversal.
| Subdomain | Source | Status | Provider / CNAME | Certificates | First Seen | Issuer(s) |
|---|---|---|---|---|---|---|
a.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
academy.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
account.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
accounting.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
accounts.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
ad.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
adfs.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
admin.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
admin1.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
admin2.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
alert.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
alerts.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
alpha.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
analytics.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
ap-south.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
ap.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
apac.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
api.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
api1.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
api2.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
api3.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
apigw.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
apis.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
apm.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
app.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
app1.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
app2.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
appointments.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
apps.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
archive.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
archives.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
asia.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
assets.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
atom.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
auth.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
auth0.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
autoconfig.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
autodiscover.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
b.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
backup.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
backup1.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
backup2.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
beta.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
bi.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
bigdata.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
billing.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
bitbucket.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
blob.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
blog.okplay.ph
|
DNS | Current | — | — | — | — |
booking.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
broker.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
bucket.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
build.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
builds.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
c.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
ca.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
cache.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
cal.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
calendar.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
campaign.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
campaigns.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
careers.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
cart.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
catalog.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
cd.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
cdn.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
cdn1.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
cdn2.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
cdn3.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
cert.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
certs.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
chat.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
checkout.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
ci.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
client.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
clients.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
cloud.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
cms.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
cname.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
code.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
community.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
compliance.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
conference.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
config.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
configuration.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
confluence.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
connect.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
console.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
containers.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
content.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
corp.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
corporate.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
courses.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
cpanel.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
crl.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
crm.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
d.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
dashboard.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
data.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
data1.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
data2.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
database.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
datadog.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
db.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
db1.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
db2.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
dedicated.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
demo.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
deploy.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
deployment.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
dev.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
dev1.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
dev2.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
develop.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
developer.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
developers.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
devices.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
devops.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
directory.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
discuss.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
discussions.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
dns.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
dns1.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
dns2.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
dnscheck.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
dnstool.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
doc.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
docker.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
docs.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
documentation.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
download.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
downloads.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
drupal.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
e.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
ecommerce.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
edge.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
edge1.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
edge2.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
education.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
elastic.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
elasticsearch.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
email.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
emea.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
endpoint.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
erp.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
es.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
etl.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
eu-west.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
eu.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
event.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
events.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
exchange.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
ext.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
f.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
faq.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
feed.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
feedback.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
feeds.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
file.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
files.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
finance.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
firewall.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
forms.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
forum.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
forums.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
ftp.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
ftp1.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
ftp2.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
fw.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
gateway.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
geo.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
gis.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
git.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
github.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
gitlab.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
go.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
grafana.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
graphql.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
gw.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
gw1.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
gw2.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
haproxy.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
health.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
healthcheck.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
help.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
helpdesk.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
hiring.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
host.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
hosting.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
hq.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
hr.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
hris.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
hub.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
id.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
identity.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
image.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
images.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
imap.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
img.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
int.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
internal.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
intranet.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
inventory.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
investor.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
investors.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
invoice.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
ir.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
it.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
itsm.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
itsupport.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
jenkins.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
jira.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
jobs.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
k8s.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
kafka.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
kb.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
kibana.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
kong.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
kubernetes.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
lab.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
labs.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
lan.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
lb.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
ldap.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
learn.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
learning.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
legal.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
link.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
links.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
live.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
lms.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
loadbalancer.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
location.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
log.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
login.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
logs.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
lookup.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
m.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
mail.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
mail1.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
mail2.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
mail3.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
mailgw.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
mailhost.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
mailrelay.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
mailserver.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
manage.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
management.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
manager.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
map.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
maps.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
marketing.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
mdm.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
media.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
meet.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
meeting.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
memcached.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
metrics.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
microservices.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
mobile.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
mongo.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
mongodb.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
monitor.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
monitoring.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
mq.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
mta.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
mx.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
mx1.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
mx2.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
mx3.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
mx4.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
mx5.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
mxtoolbox.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
my.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
myaccount.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
mysql.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
na.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
nagios.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
net.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
netadmin.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
nettool.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
nettools.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
network.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
news.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
nginx.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
node1.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
node2.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
node3.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
notifications.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
notify.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
ns.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
ns1.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
ns2.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
ns3.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
ns4.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
ns5.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
ns6.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
o365.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
oauth.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
object.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
ocsp.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
office.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
okta.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
order.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
orders.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
origin.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
origin1.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
origin2.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
outlook.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
owa.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
panel.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
partner.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
partners.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
pay.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
payment.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
payments.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
payroll.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
pbx.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
phone.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
photos.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
pingdom.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
pki.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
plesk.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
policies.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
policy.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
pop.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
pop3.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
portal.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
portal2.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
postgres.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
pre.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
preprod.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
press.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
preview.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
primary.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
print.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
printer.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
privacy.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
private.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
product.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
products.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
profile.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
prometheus.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
promo.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
proxy.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
proxy1.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
proxy2.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
public.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
qa.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
queue.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
r.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
ra.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
rabbitmq.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
rancher.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
realtime.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
recruit.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
redirect.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
redis.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
register.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
registry.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
relay.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
relay1.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
releases.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
remote.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
repo.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
report.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
reporting.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
reports.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
repos.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
reservations.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
rest.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
rss.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
rt.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
s3.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
sandbox.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
sandbox1.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
sandbox2.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
scan.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
scanner.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
schedule.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
scp.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
search.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
secondary.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
secrets.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
secure.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
server.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
server1.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
server2.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
server3.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
service.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
servicedesk.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
services.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
sftp.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
share.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
shop.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
signin.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
signup.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
sip.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
slack.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
smtp.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
smtp1.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
smtp2.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
socket.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
solr.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
speedtest.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
sql.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
srv.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
srv1.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
srv2.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
ssh.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
ssl.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
sso.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
stage.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
staging.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
static.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
static1.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
static2.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
statistics.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
stats.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
status.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
statuspage.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
stg.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
storage.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
store.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
stream.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
streaming.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
support.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
support2.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
survey.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
surveys.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
svc.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
svn.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
swift.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
sysadmin.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
syslog.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
talent.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
teams.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
techsupport.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
tel.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
telecom.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
terms.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
test.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
test1.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
test2.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
testing.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
ticket.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
tickets.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
tls.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
tool.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
tools.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
trace.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
tracing.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
tracking.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
training.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
uat.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
upload.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
uploads.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
uptime.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
url.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
us-east.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
us-west.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
us.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
utility.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
varnish.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
vault.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
vendor.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
vendors.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
video.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
videos.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
voip.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
vpn.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
vpn1.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
vpn2.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
vpn3.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
vps.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
waf.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
wan.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
warehouse.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
web.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
web1.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
web2.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
webapi.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
webapp.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
webex.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
webhost.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
webinar.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
webinars.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
webmail.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
webproxy.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
webserver.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
websocket.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
webtool.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
webtools.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
whm.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
whois.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
wiki.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
wordpress.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
work.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
worker.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
worker1.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
worker2.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
workspace.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
wp.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
ws.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
www.okplay.ph
|
DNS | Current | — | — | — | — |
www1.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
www2.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
www3.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
xml.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
zabbix.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
zoom.okplay.ph
|
DNS | Current |
3c74tnj6sru9.okplay.ph.eo.dnse5.com
|
— | — | — |
Δ 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 66%
Currency 73/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 Degraded
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 |
|---|---|---|---|---|
| NS | 20925s |
1 day (86400s) |
medium | NS TTL is below typical — observed 20925s, 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. |
| TXT | 292s |
1 hour (3600s) |
high | TXT TTL is below typical — observed 292s, 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. |
| CAA | 292s |
1 hour (3600s) |
high | CAA TTL is below typical — observed 292s, 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. |
| A | 290s |
1 hour (3600s) |
high | A TTL is below typical — observed 290s, 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. |
| SOA | 1792s |
1 hour (3600s) |
medium |
SOA TTL is below typical — observed 1792s, 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.
Provider Note: Cloudflare manages SOA timers automatically. Free/Pro/Business plans cannot modify SOA values. Observed TTL (1792s) is set by Cloudflare, not the zone administrator. See RFC 1912 §2.2 for recommended SOA timer values.
|
| MX | 10 minutes (600s) |
1 hour (3600s) |
medium | MX TTL is below typical — observed 10 minutes (600s), typical value is 1 hour (3600s). Short TTLs increase DNS query volume but enable faster propagation. If you are preparing for a migration or need rapid failover, this may be intentional (RFC 1035 §3.2.1). For steady-state production, consider 3600 seconds per NIST SP 800-53 SI-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
collins.ns.cloudflare.com
Serial
2411402340
Admin
dns.cloudflare.com
Provider
Cloudflare
| Timer | Value | RFC 1912 Range |
|---|---|---|
| Refresh | 10000s | 1,200–43,200s (20 min – 12 hrs) |
| Retry | 2400s | Fraction of Refresh |
| Expire | 604800s | 1,209,600–2,419,200s (14–28 days) |
| Minimum (Neg. Cache) | 1800s | 300–86,400s (5 min – 1 day) |
Expire: SOA Expire is 7 days (604800s). RFC 1912 §2.2 recommends 1,209,600–2,419,200 seconds (14–28 days). If the primary nameserver becomes unreachable, secondary nameservers will stop serving this zone after only 7 days (604800s). Cloudflare's anycast architecture reduces the practical risk, but this value departs from the RFC recommendation.
Independent RFC compliance assessment for Cloudflare. 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.
SOA Expire below RFC 1912 recommendation
RFC 1912 §2.2
Cloudflare sets SOA Expire to 604,800 seconds (7 days). RFC 1912 §2.2 recommends 1,209,600–2,419,200 seconds (14–28 days). This means secondary nameservers stop serving the zone sooner if the primary becomes unreachable. Cloudflare's position is that their anycast architecture makes traditional zone transfer semantics less relevant. SOA timers are not editable on Free, Pro, or Business plans.
Below RFC recommendation
Proxied record TTLs fixed at 300s
RFC 2181 §5.2
Cloudflare overrides the zone administrator's TTL to 300 seconds for all proxied (orange-cloud) records. RFC 2181 §5.2 requires TTL uniformity within an RRset but does not mandate a specific value. As the authoritative server, Cloudflare is technically within its rights, but the administrator loses TTL control. This can affect ACME DNS-01 challenges and automation workflows that depend on rapid propagation.
Technically compliant, but overrides administrator intent
Non-standard SOA serial format
RFC 1912 §2.2
RFC 1912 recommends YYYYMMDDNN format for SOA serial numbers (e.g., 2026022501). Cloudflare uses a proprietary serial number format that does not encode the date. RFC 1035 only requires the serial to increment on changes, so this is compliant with the mandatory standard but breaks the convention relied on by monitoring tools.
Compliant with RFC 1035, deviates from RFC 1912 convention
Negative cache TTL delays new records
RFC 2308 §5
Cloudflare's SOA MINIMUM (negative cache TTL) is 1,800–3,600 seconds (30–60 minutes). This controls how long resolvers cache NXDOMAIN responses. Newly created DNS records — including ACME DNS-01 challenge TXT records for Let's Encrypt — may be invisible for up to 1 hour even after creation. This causes certificate issuance failures for automation tools like cert-manager and Traefik. Workaround: pre-create placeholder records before they're needed. This is RFC-compliant but aggressive compared to the 300–900 seconds common at other providers.
RFC-compliant, but causes real-world automation failures
Historical RFC 2181 §5.2 violation: TTL mismatch in CNAME RRsets
RFC 2181 §5.2
In February 2022, Cloudflare's resolver (1.1.1.1) returned CNAME responses with mismatched TTLs within the same RRset — including cases where one TTL was zero and another was non-zero. RFC 2181 §5.2 explicitly states: 'the TTLs of all RRs in an RRSet must be the same.' systemd-resolved (used by Arch Linux, Ubuntu, Fedora, and most modern Linux distributions) correctly rejected these responses per the RFC, causing widespread DNS resolution failures. Cloudflare acknowledged the issue and it appears to have been fixed, but it demonstrated that Cloudflare's DNS infrastructure can deviate from RFC requirements in ways that break compliant resolver implementations.
Was a documented RFC violation — appears resolved
DNS Intelligence
What does DNS look like right now — and what changed over time?
DNS Evidence Diff Side-by-side comparison
Resolver Records
(Public DNS cache)
Authoritative Records
(Source of truth)
A
Synchronized
2 / 2 records
104.18.30.191
104.18.31.191
104.18.31.191
104.18.30.191
AAAA
0 / 0 records
No records
No records
0 issue "letsencrypt.org"
0 issue "comodoca.com"
0 issue "ssl.com"
0 issue "digicert.com; cansignhttpexchanges=yes"
0 issuewild "comodoca.com"
0 issue "letsencrypt.org"
0 issuewild "letsencrypt.org"
0 issue "pki.goog; cansignhttpexchanges=yes"
0 issue "pki.goog; cansignhttpexchanges=yes"
0 issue "sectigo.com"
0 issue "sectigo.com"
0 issue "ssl.com"
0 issue "digicert.com; cansignhttpexchanges=yes"
0 issuewild "comodoca.com"
0 issue "comodoca.com"
0 issuewild "digicert.com; cansignhttpexchanges=yes"
0 issuewild "pki.goog; cansignhttpexchanges=yes"
0 issuewild "letsencrypt.org"
0 issuewild "digicert.com; cansignhttpexchanges=yes"
0 issuewild "pki.goog; cansignhttpexchanges=yes"
0 issuewild "ssl.com"
0 issuewild "ssl.com"
v=DMARC1; p=none; rua=mailto:dmarc-reports@okplay.ph;
v=DMARC1; p=none; rua=mailto:dmarc-reports@okplay.ph;
1 mx1.larksuite.com.
1 mx1.larksuite.com.
10 mx3.larksuite.com.
10 mx3.larksuite.com.
5 mx2.larksuite.com.
5 mx2.larksuite.com.
collins.ns.cloudflare.com.
collins.ns.cloudflare.com.
dane.ns.cloudflare.com.
dane.ns.cloudflare.com.
collins.ns.cloudflare.com. dns.cloudflare.com. 2411402340 10000 2400 604800 1800
collins.ns.cloudflare.com. dns.cloudflare.com. 2411402340 10000 2400 604800 1800
google-site-verification=DserNiDUrQIE9wG4H8cX7txvn147b5Ng0TZCTYLBsQQ
google-site-verification=DserNiDUrQIE9wG4H8cX7txvn147b5Ng0TZCTYLBsQQ
v=spf1 +include:spf.onlarksuite.com -all
v=spf1 +include:spf.onlarksuite.com -all
verification-code-site-App_lark=UcmHxrJHvRH39LJW0TpR
verification-code-site-App_lark=UcmHxrJHvRH39LJW0TpR
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.
0e87e07ad37b75e4a05555febb9d0200c1176f364d43c479f9792f675d1e30623dbb37057e380c1cebc75c978665bfab828227907320aba56a8135f7a21c39f4
Evaluations reference 12 RFCs. Methods are reproducible using the verification commands provided. Results reflect DNS state at 12 Aug 2026, 13:20 UTC.
Download the intelligence dump and verify its integrity, like you would a Kali ISO or any critical artifact. The SHA-3-512 checksum covers every byte of the download — deterministic serialization ensures identical hashes across downloads.
After downloading, verify with any of these commands:
Tip: cd ~/Downloads first (or wherever you saved the files).
OpenSSL + Sidecar (macOS, Linux, WSL)
cat dns-intelligence-okplay.ph.json.sha3 && echo '---' && openssl dgst -sha3-512 dns-intelligence-okplay.ph.json
Python 3 (cross-platform)
python3 -c "import hashlib; print(hashlib.sha3_512(open('dns-intelligence-okplay.ph.json','rb').read()).hexdigest())"
sha3sum (coreutils 9+)
sha3sum -a 512 dns-intelligence-okplay.ph.json
Compare the output against the
.sha3 file or the checksum API at /api/analysis/18274/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 okplay.ph. 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 okplay.ph A
Query AAAA records (IPv6) RFC 1035
dig +noall +answer okplay.ph AAAA
Query MX records (mail servers) RFC 1035
dig +noall +answer okplay.ph MX
Query NS records (nameservers) RFC 1035
dig +noall +answer okplay.ph NS
Query TXT records RFC 1035
dig +noall +answer okplay.ph TXTEmail Authentication
Check SPF record RFC 7208
dig +short okplay.ph TXT | grep -i spf
Check DMARC policy RFC 7489
dig +short _dmarc.okplay.ph TXT
Check DKIM key for selector 'default' RFC 6376
dig +short default._domainkey.okplay.ph TXT
Check DKIM key for selector 'google' RFC 6376
dig +short google._domainkey.okplay.ph TXT
Check DKIM key for selector 'selector1' RFC 6376
dig +short selector1._domainkey.okplay.ph TXT
Check DKIM key for selector 'selector2' RFC 6376
dig +short selector2._domainkey.okplay.ph TXTDomain Security
Check DNSSEC DNSKEY records RFC 4035
dig +dnssec +noall +answer okplay.ph DNSKEY
Check DNSSEC DS records RFC 4035
dig +noall +answer okplay.ph DS
Validate DNSSEC chain (requires DNSSEC-validating resolver) RFC 4035
dig +dnssec +cd okplay.ph A @1.1.1.1Transport Security
Check TLSA record for mx1.larksuite.com RFC 7672
dig +noall +answer _25._tcp.mx1.larksuite.com TLSA
Check TLSA record for mx3.larksuite.com RFC 7672
dig +noall +answer _25._tcp.mx3.larksuite.com TLSA
Check TLSA record for mx2.larksuite.com RFC 7672
dig +noall +answer _25._tcp.mx2.larksuite.com TLSA
Verify TLS certificate on primary MX (mx1.larksuite.com) RFC 6698
openssl s_client -starttls smtp -connect mx1.larksuite.com:25 -servername mx1.larksuite.com 2>/dev/null | openssl x509 -noout -subject -dates
Check MTA-STS DNS record RFC 8461
dig +short _mta-sts.okplay.ph TXT
Fetch MTA-STS policy file RFC 8461
curl -sL https://mta-sts.okplay.ph/.well-known/mta-sts.txt
Check TLS-RPT record RFC 8460
dig +short _smtp._tls.okplay.ph TXTBrand & Trust
Check BIMI record BIMI Draft
dig +short default._bimi.okplay.ph TXT
Check CAA records (certificate authority authorization) RFC 8659
dig +noall +answer okplay.ph CAADNS Records
Check HTTPS/SVCB records RFC 9460
dig +noall +answer okplay.ph HTTPSDomain Security
Check CDS/CDNSKEY automation records RFC 7344
dig +noall +answer okplay.ph CDSInfrastructure Intelligence
RDAP domain registration lookup RFC 9083
curl -sL 'https://rdap.org/domain/okplay.ph' | python3 -m json.tool | head -50Transport Security
Test STARTTLS on primary MX (mx1.larksuite.com) RFC 3207
openssl s_client -starttls smtp -connect mx1.larksuite.com:25 -servername mx1.larksuite.com </dev/null 2>/dev/null | head -5Infrastructure Intelligence
Search Certificate Transparency logs RFC 6962
curl -s 'https://crt.sh/?q=%25.okplay.ph&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://okplay.ph/.well-known/security.txt | head -20AI Surface
Check for llms.txt
curl -sI https://okplay.ph/llms.txt | head -5
Check robots.txt for AI crawler rules
curl -s https://okplay.ph/robots.txt | grep -i -E 'GPTBot|ChatGPT|Claude|Anthropic|Google-Extended|CCBot|PerplexityBot'Infrastructure Intelligence
ASN lookup for 104.18.30.191 (Team Cymru)
dig +short 191.30.18.104.origin.asn.cymru.com TXT
ASN lookup for 104.18.31.191 (Team Cymru)
dig +short 191.31.18.104.origin.asn.cymru.com TXT
Commands use
dig, openssl, and curl — standard tools available on macOS, Linux, and WSL. Results may vary slightly due to DNS propagation timing and resolver caching.
Intelligence Confidence Audit Engine
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 okplay.ph Adig +noall +answer okplay.ph AAAAdig +noall +answer okplay.ph MXdig +noall +answer okplay.ph NSdig +noall +answer okplay.ph TXTEmail Authentication
dig +short okplay.ph TXT | grep -i spfdig +short _dmarc.okplay.ph TXTdig +short default._domainkey.okplay.ph TXTdig +short google._domainkey.okplay.ph TXTdig +short selector1._domainkey.okplay.ph TXTdig +short selector2._domainkey.okplay.ph TXTDomain Security
dig +dnssec +noall +answer okplay.ph DNSKEYdig +noall +answer okplay.ph DSdig +dnssec +cd okplay.ph A @1.1.1.1Transport Security
dig +noall +answer _25._tcp.mx1.larksuite.com TLSAdig +noall +answer _25._tcp.mx3.larksuite.com TLSAdig +noall +answer _25._tcp.mx2.larksuite.com TLSAopenssl s_client -starttls smtp -connect mx1.larksuite.com:25 -servername mx1.larksuite.com 2>/dev/null | openssl x509 -noout -subject -datesdig +short _mta-sts.okplay.ph TXTcurl -sL https://mta-sts.okplay.ph/.well-known/mta-sts.txtdig +short _smtp._tls.okplay.ph TXTBrand & Trust
dig +short default._bimi.okplay.ph TXTdig +noall +answer okplay.ph CAADNS Records
dig +noall +answer okplay.ph HTTPSDomain Security
dig +noall +answer okplay.ph CDSInfrastructure Intelligence
curl -sL 'https://rdap.org/domain/okplay.ph' | python3 -m json.tool | head -50Transport Security
openssl s_client -starttls smtp -connect mx1.larksuite.com:25 -servername mx1.larksuite.com </dev/null 2>/dev/null | head -5Infrastructure Intelligence
curl -s 'https://crt.sh/?q=%25.okplay.ph&output=json' | python3 -c "import json,sys; [print(e['name_value']) for e in json.load(sys.stdin)]" | sort -u | head -20curl -sL https://okplay.ph/.well-known/security.txt | head -20AI Surface
curl -sI https://okplay.ph/llms.txt | head -5curl -s https://okplay.ph/robots.txt | grep -i -E 'GPTBot|ChatGPT|Claude|Anthropic|Google-Extended|CCBot|PerplexityBot'Infrastructure Intelligence
dig +short 191.30.18.104.origin.asn.cymru.com TXTdig +short 191.31.18.104.origin.asn.cymru.com TXT