Skip to content

Hostname

gsdiagnostics.com.ph

Last fetched

gsdiagnostics.com.ph resolves to 45.79.222.138, announced in 45.79.192.0/19 by AKAMAI-LINODE-AP - Akamai Connected Cloud in US. gsdiagnostics.com.ph is listed by 1 threat feed; reconciled level HIGH.

Threat posture

40threat score (procedure-native scale)

HIGH

Listed by 1 threat feed. At least one source recommends blocking.

Threat feeds listing this
1
Verdict coverage
malicious-evidenced
First seen on a feed
Wed, 26 Aug 2026 14:49:47 GMT
Last seen on a feed
Fri, 18 Sep 2026 00:11:39 GMT

Nutrition Label

WHISPER CANON · gsdiagnostics.com.phRouting diversity2.4/10Peering density6.3/10MOAS conflict✓ noneThreat-feed listings8.0/10WHOIS transparency0.0/10Resolver footprint9.0/10canon.whisper.security/host/gsdiagnostics.com.ph

Resolution chain

IPv6 resolution

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

Attribution

hivelocity

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for gsdiagnostics.com.ph. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

Subdomains

Mail and authentication

Nameservers

  • ns1.parklogic.com
  • ns2.parklogic.com
  • ns2.cuhk.edu.hk
  • ns4.apnic.net
  • ph.communitydns.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
  • 1.ns.ph
  • ns1.zoom.ph
  • ns2.zoom.ph
  • ns3.zoom.ph

MX records

  • mx156.hostedmxserver.com
  • gsdiagnostics.com.ph

SPF policy

  • include: relay.mailchannels.net
  • a: gsdiagnostics.com.ph
  • mx: gsdiagnostics.com.ph
  • ip: 46.21.149.90

Threat-feed evidence

History

Related pages

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