Skip to content

Hostname

lowadi.com

Last fetched

lowadi.com resolves to 172.205.74.146, announced in 172.200.0.0/13 by MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation in IE. lowadi.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 · lowadi.comRouting diversity1.5/10Peering density8.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/lowadi.com

Resolution chain

IPv6 resolution

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

Attribution

Azure

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:81
Registrant organisation
charlie guillemot
Contact emails
0d9fe3662c743a699bf542f0ef29ebda-636439@contact.gandi.net, 286824cdd153f116b0a531db838c1497-636439@contact.gandi.net, 5ec1fa385a76e8d95e45a37e6d73ac37-40758660@contact.gandi.net, c843581ad694f24b4a80b1765221ce63-636439@contact.gandi.net

Subdomains

Subdomain
itkdlu.lowadi.com
m.lowadi.com
preprod.lowadi.com
www.lowadi.com

Showing 4 of 5. View all subdomains →

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Sample inbound links

Mail and authentication

Nameservers

  • ns1-02.azure-dns.com
  • ns4-02.azure-dns.info
  • ns2-02.azure-dns.net
  • a.gtld-servers.net
  • b.gtld-servers.net
  • c.gtld-servers.net
  • d.gtld-servers.net
  • e.gtld-servers.net
  • f.gtld-servers.net
  • g.gtld-servers.net
  • h.gtld-servers.net
  • i.gtld-servers.net
  • j.gtld-servers.net
  • k.gtld-servers.net
  • l.gtld-servers.net
  • m.gtld-servers.net
  • ns3-02.azure-dns.org

SPF policy

  • include: spf.protection.outlook.com
  • redirect: owlient.eu

Threat-feed evidence

History

Related pages

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