Skip to content

Hostname

polilogistics.com

Last fetched

polilogistics.com resolves to 1 IPv4 address operated by STSB-AS-AP - Serverfreak Technologies Sdn Bhd in MY. WHOIS lists iana:460 as the registrar.

Nutrition Label

WHISPER CANON · polilogistics.comRouting diversity1.5/10Peering density2.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/polilogistics.com

Resolution chain

polilogistics.com resolves to 1 distinct IPv4 address via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.

IPPrefixASNOperatorCountry
103.27.73.150103.27.73.0/24AS150172STSB-AS-AP - Serverfreak Technologies Sdn BhdMY

WHOIS identity

Registrar
iana:460
Organization
har ry
Contact emails

Subdomains

25 observed subdomains of polilogistics.com.

Subdomain
australiaservicecentre.polilogistics.com
autodiscover.polilogistics.com
caffecoffea.polilogistics.com
cargoagentnetwork.polilogistics.com
cpanel.polilogistics.com
cpcalendars.polilogistics.com
cpcontacts.polilogistics.com
gamudawalk.polilogistics.com
kbbstech.polilogistics.com
liewtrainingcentre.polilogistics.com
loseafood.polilogistics.com
mail.polilogistics.com
qlseafood.polilogistics.com
seafoodtrading.polilogistics.com
webdisk.polilogistics.com
webmail.polilogistics.com
www.polilogistics.com

Showing 17 of 25. View all subdomains →

Web-graph footprint

Distinct hostnames that link to or from polilogistics.com in the public web crawl.

26 sites linked to from this hostname.

Sample inbound links

Sample outbound links

Threat posture

History

Mail and authentication

MX records

  • polilogistics.com

SPF policy

9 SPF mechanisms authorising senders for polilogistics.com.

MechanismTarget
SPF_Apolilogistics.com
SPF_INCLUDEspf.sfdns.net
SPF_IP103.27.73.150
SPF_IP103.27.73.30
SPF_IP220.158.200.190
SPF_IP220.158.200.193
SPF_IP220.158.200.80
SPF_IP220.158.200.81
SPF_MXpolilogistics.com

Related pages

Pivot deeper into the graph from polilogistics.com.

Cypher and MCP

Reproduce the resolution chain directly against graph.whisper.security:

MATCH (h:HOSTNAME {name: "polilogistics.com"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
      -[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.