Hostname
psgemilang.com
Last fetched
psgemilang.com resolves to 103.16.132.117, announced in 103.16.132.0/24 by IDNIC-MAYATAMA-AS-ID - PT Mayatama Solusindo in ID. psgemilang.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
IPv6 resolution
No AAAA record for psgemilang.com is recorded in WhisperGraph.
Attribution
pt mayatama solusindo
ORIGIN_AS
WHOIS identity
- Registrar
- iana:1675
- Registrant organisation
- domain data guard
- Contact emails
- noreply@domaindataguard.com
Subdomains
| Subdomain |
|---|
| mail.psgemilang.com |
| mail2.psgemilang.com |
| ns1.psgemilang.com |
| ns2.psgemilang.com |
| ns3.psgemilang.com |
| www.psgemilang.com |
Showing 6 of 6 subdomains (6 per page).
Mail and authentication
Nameservers
- ns1.psgemilang.com
- ns2.psgemilang.com
- ns3.psgemilang.com
- ns1.mayatama.net
- ns2.mayatama.net
- ns3.mayatama.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
MX records
- mail.psgemilang.com
- mail2.psgemilang.com
SPF policy
- ip: 175.111.112.0/21
- ip: 103.16.132.0/24
- ip: 203.153.20.0/24
- ip: 103.102.249.0/24
- include: _spf.google.com
- a: psgemilang.com
- mx: psgemilang.com
- ip: 103.102.249.2
- ip: 103.102.249.3
- ip: 103.102.249.4
- ip: 103.16.132.162
- ip: 103.16.132.163
- ip: 103.16.132.167
- ip: 103.16.132.187
- ip: 103.16.132.253
- ip: 103.16.132.75
- ip: 175.111.112.2
- ip: 175.111.112.3
- ip: 175.111.112.4
- ip: 175.111.112.7
- ip: 175.111.112.8
- ip: 175.111.112.9
- ip: 3.3.3.1
Threat-feed evidence
History
Related pages
Pivot from psgemilang.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: "psgemilang.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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.