Hostname
parlament.mt
Last fetched
parlament.mt resolves to 162.159.140.137, announced in 162.159.128.0/19 by CLOUDFLARENET - Cloudflare, Inc. in CA. parlament.mt 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
- 162.159.140.137
162.159.128.0/19 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.66.0.135
172.66.0.0/22 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
No AAAA record for parlament.mt is recorded in WhisperGraph.
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for parlament.mt. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.
Subdomains
| Subdomain |
|---|
| pqcms.parlament.mt |
| www.parlament.mt |
Showing 2 of 3. 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-05.azure-dns.com
- ns4-05.azure-dns.info
- ns2-05.azure-dns.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
- ns3-05.azure-dns.org
MX records
- parlament-mt.mail.protection.outlook.com
SPF policy
- include: spf.protection.outlook.com
- a: gsmtp3.serversdns.gov.mt
- a: gsmtp6.serversdns.gov.mt
- a: gsmtp7.serversdns.gov.mt
- mx: parlament.mt
- ip: 217.30.99.101
- ip: 217.30.99.102
- ip: 217.30.99.103
- ip: 217.30.99.104
Threat-feed evidence
History
Related pages
Pivot from parlament.mt 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: "parlament.mt"})-[: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.