Skip to content

Hostname

playd.com

Last fetched

playd.com resolves to 219.240.12.52, announced in 219.240.0.0/15 by SKB-AS-KR - SK Broadband Co Ltd in KR. playd.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · playd.comRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/playd.com

Resolution chain

IPv6 resolution

No AAAA record for playd.com is recorded in WhisperGraph.

Attribution

sk broadband

ORIGIN_AS

WHOIS identity

Registrar
iana:244
Registrant organisation
kari bian
Contact emails
contact4040@aol.com, itso-group@playd.com, junyoung-hyun@playd.com, sehyeon.seoung@nsm.co.kr

Subdomains

Subdomain
capig.playd.com
ehr-mobile.playd.com
ehr.playd.com
gw.playd.com
lib.playd.com
new.playd.com
sign.playd.com
worki.playd.com
www.playd.com

Showing 9 of 9 subdomains (9 per page).

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Sample inbound links

Sample outbound links

Mail and authentication

Nameservers

  • ns1-1.ns-ncloud.com
  • ns1-2.ns-ncloud.com
  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • d.root-servers.net
  • e.root-servers.net
  • f.root-servers.net
  • g.root-servers.net
  • h.root-servers.net
  • i.root-servers.net
  • j.root-servers.net
  • k.root-servers.net
  • l.root-servers.net
  • m.root-servers.net

MX records

  • kr1-aspmx1.worksmobile.com
  • kr1-aspmx2.worksmobile.com

SPF policy

  • ip: 114.202.247.0/24
  • ip: 222.122.81.0/24
  • include: spf.naver.com
  • include: spf.worksmobile.com
  • ip: 121.254.168.123
  • ip: 219.240.12.37
  • ip: 61.37.123.84

Threat-feed evidence

History

Related pages

Pivot from playd.com into the addresses, networks and registries it depends on.

Cypher and MCP

Reproduce this hostname's resolution chain against graph.whisper.security:

MATCH (h:HOSTNAME {name: "playd.com"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.