Hostname
lgus.ph
Last fetched
lgus.ph resolves to 45.79.222.138, announced in 45.79.192.0/19 by AKAMAI-LINODE-AP - Akamai Connected Cloud in US. lgus.ph is listed by 1 threat feed; reconciled level HIGH.
Threat posture
40threat score (procedure-native scale)
HIGHListed 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
- Tue, 22 Sep 2026 23:26:40 GMT
Nutrition Label
Resolution chain
- 45.79.222.138
45.79.192.0/19 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Atlanta, US
- 5.9.153.8
5.9.0.0/16 · HETZNER-AS - Hetzner Online GmbH · Falkenstein, DE
- 172.239.48.136
172.239.32.0/19 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
- 172.238.172.68
172.238.160.0/19 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
- 172.239.193.190
172.239.192.0/19 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Chicago, US
IPv6 resolution
No AAAA record for lgus.ph is recorded in WhisperGraph.
Attribution
akamai
MAIL_RECEIVER, ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for lgus.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
- ns13.hostarchives.com
- ns14.hostarchives.com
- 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
- f.root-servers.net
- h.root-servers.net
- k.root-servers.net
- m.root-servers.net
- ns1.lgus.ph
- ns2.lgus.ph
- 1.ns.ph
MX records
- mx156.hostedmxserver.com
- lgus.ph
SPF policy
- a: lgus.ph
- mx: lgus.ph
- ip: 138.201.27.66
- ip: 148.251.177.20
- ip: 194.163.140.215
- ip: 5.9.153.8
- ip: 95.217.48.81
- ip: 95.217.48.86
Threat-feed evidence
History
Related pages
Pivot from lgus.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: "lgus.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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.