Hostname
mdengineering.co.uk
Last fetched
mdengineering.co.uk resolves to 4 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in IE. WHOIS lists registrar:gradwell communications limited t/a gradwell communications limited as the registrar.
Nutrition Label
Resolution chain
mdengineering.co.uk resolves to 4 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 52.208.83.67 | 52.208.0.0/13 | AS16509 | AMAZON-02 - Amazon.com, Inc. | IE |
| 54.216.221.176 | 54.216.0.0/15 | AS16509 | AMAZON-02 - Amazon.com, Inc. | IE |
| 54.247.123.195 | 54.247.0.0/17 | AS16509 | AMAZON-02 - Amazon.com, Inc. | IE |
| 99.80.207.61 | 99.80.0.0/15 | AS16509 | AMAZON-02 - Amazon.com, Inc. | IE |
WHOIS identity
- Registrar
- registrar:gradwell communications limited t/a gradwell communications limited
- Organization
- m d engineering
- Contact emails
- —
Subdomains
2 observed subdomains of mdengineering.co.uk.
Web-graph footprint
Distinct hostnames that link to or from mdengineering.co.uk in the public web crawl.
7 sites linked to from this hostname.
Sample inbound links
Threat posture
History
Mail and authentication
SPF policy
9 SPF mechanisms authorising senders for mdengineering.co.uk.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | spf.protection.outlook.com |
| SPF_IP | 31.121.41.30 |
| SPF_IP | 81.187.100.134 |
| SPF_IP | 81.187.107.118 |
| SPF_IP | 82.71.134.46 |
| SPF_IP | 87.242.137.230 |
| SPF_IP | 87.242.211.182 |
| SPF_IP | 94.229.129.170 |
| SPF_MX | mdengineering.co.uk |
Related pages
Pivot deeper into the graph from mdengineering.co.uk.
- IP · 52.208.83.67
- ASN · AS16509AMAZON-02 - Amazon.com, Inc.
- Registrar · registrar:gradwell communications limited t/a gradwell communications limited
- Country · IE
- Apex domain · co.uk
- TLD · .uk
- Browse hostnames · md…
- Glossary · What is a hostname?
- Whisper Internet Directory — home
- Live MOAS conflicts feed
- Threat feed · Spamhaus DROP
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "mdengineering.co.uk"})-[: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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.