Hostname
maqsam.com
Last fetched
maqsam.com resolves to 31.43.160.6, announced in 31.43.160.0/24 by AMAZON-02 - Amazon.com, Inc. in NL. maqsam.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
- 31.43.160.6
31.43.160.0/24 · AMAZON-02 - Amazon.com, Inc. · Amsterdam, NL
- 31.43.161.6
31.43.161.0/24 · AMAZON-02 - Amazon.com, Inc. · Amsterdam, NL
IPv6 resolution
No AAAA record for maqsam.com is recorded in WhisperGraph.
Attribution
amazon com
ORIGIN_AS
WHOIS identity
- Registrar
- iana:1068
- Registrant organisation
- 1&1 internet
- Contact emails
- privacy@1and1.com, 5e619f83e6de46a6af8853a54cb72c1a.protect@whoisguard.com, 1d63d0c190a74fc1901d13262e780f55.protect@withheldforprivacy.com, 985836e461a140f884ef1156ff8455a1.protect@withheldforprivacy.com
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
- ns-146.awsdns-18.com
- ns-587.awsdns-09.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
- ns-1507.awsdns-60.org
- ns-1685.awsdns-18.co.uk
MX records
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- alt3.aspmx.l.google.com
- alt4.aspmx.l.google.com
SPF policy
- include: _spf.google.com
- include: 143224266.spf03.hubspotemail.net
- include: zcsend.net
Threat-feed evidence
History
Related pages
Pivot from maqsam.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: "maqsam.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.