Skip to content

Hostname

creamsilk.com.ph

Last fetched

creamsilk.com.ph resolves to 20.238.208.21, announced in 20.192.0.0/10 by MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation in NL. creamsilk.com.ph 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 · creamsilk.com.phRouting diversity1.5/10Peering density8.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency6.7/10Resolver footprint8.3/10canon.whisper.security/host/creamsilk.com.ph

Resolution chain

IPv6 resolution

No AAAA record for creamsilk.com.ph is recorded in WhisperGraph.

Attribution

Azure

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:106
Registrant organisation
grace estrella-damias
Contact emails
gra...@...

Subdomains

Subdomain
mail.creamsilk.com.ph
mailing.creamsilk.com.ph
www.creamsilk.com.ph

Showing 3 of 6. View all subdomains →

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-44.azure-dns.com
  • ns4-44.azure-dns.info
  • ns2-44.azure-dns.net
  • 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
  • ns3-44.azure-dns.org

MX records

  • mail.dms.unileverservices.com

SPF policy

  • include: amazonaws.com
  • include: amazonses.com
  • include: _spf.google.com
  • include: mail.dms.unileverservices.com
  • include: servers.mcsv.net
  • a: creamsilk.com.ph
  • mx: creamsilk.com.ph
  • include: mail.creamsilk.com.ph

Threat-feed evidence

History

Related pages

Pivot from creamsilk.com.ph 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: "creamsilk.com.ph"})-[: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.