Hostname
autoinfo.ma
Last fetched
autoinfo.ma resolves to 68.65.121.216, announced in 68.65.121.0/24 by NAMECHEAP-NET - Namecheap, Inc. in US. autoinfo.ma 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.
Categories: Phishing
- Threat feeds listing this
- 1
- Verdict coverage
- malicious-evidenced
- First seen on a feed
- Wed, 26 Aug 2026 14:49:49 GMT
- Last seen on a feed
- Tue, 22 Sep 2026 20:26:49 GMT
Nutrition Label
Resolution chain
- 68.65.121.216
68.65.121.0/24 · NAMECHEAP-NET - Namecheap, Inc. · Dallas, US
IPv6 resolution
No AAAA record for autoinfo.ma is recorded in WhisperGraph.
Attribution
namecheap
ORIGIN_AS
WHOIS identity
- Registrar
- registrar:arcanes technologies
- Registrant organisation
- maplab
- Contact emails
- jamalmatic@gmail.com
Subdomains
| Subdomain |
|---|
| cpanel.autoinfo.ma |
| cpcalendars.autoinfo.ma |
| cpcontacts.autoinfo.ma |
| mail.autoinfo.ma |
| webdisk.autoinfo.ma |
| webmail.autoinfo.ma |
| www.autoinfo.ma |
Showing 7 of 7 subdomains (7 per page).
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
- dns1.namecheaphosting.com
- dns2.namecheaphosting.com
- 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
- mx1-hosting.jellyfish.systems
- mx2-hosting.jellyfish.systems
- mx3-hosting.jellyfish.systems
SPF policy
- include: spf.web-hosting.com
- a: autoinfo.ma
- mx: autoinfo.ma
- ip: 68.65.121.212
- ip: 68.65.121.213
Threat-feed evidence
History
Related pages
Pivot from autoinfo.ma 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: "autoinfo.ma"})-[: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.