Skip to content

Hostname

philipsbd.com

Last fetched

philipsbd.com resolves to 14.128.15.181, announced in 14.128.15.0/24 by TOMATTOSTL-AS-AP - Tomattos Technologies Ltd. in BD. philipsbd.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 · philipsbd.comRouting diversity1.5/10Peering density1.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/philipsbd.com

Resolution chain

IPv6 resolution

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

Attribution

tomattos

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrar
iana:1068
Registrant organisation
md. abul bashar
Contact emails
admin@domainregistriesfoundation.com, japanelectronicsbd@gmail.com, c3c2fb8c115547e8978c202d3786ed41.protect@withheldforprivacy.com, bashar.riversoft@gmail.com

Subdomains

Subdomain
cpanel.philipsbd.com
cpcalendars.philipsbd.com
cpcontacts.philipsbd.com
mail.philipsbd.com
webdisk.philipsbd.com
webmail.philipsbd.com
www.philipsbd.com

Showing 7 of 7 subdomains (7 per page).

Mail and authentication

Nameservers

  • ns1.ithostbd.com
  • ns2.ithostbd.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

  • philipsbd.com

SPF policy

  • include: spf.mysecurecloudhost.com
  • a: philipsbd.com
  • mx: philipsbd.com
  • ip: 14.128.15.181
  • ip: 14.128.15.191
  • ip: 172.104.190.111
  • ip: 176.9.109.10

Threat-feed evidence

History

Related pages

Pivot from philipsbd.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: "philipsbd.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.